diff options
Diffstat (limited to '.github/ISSUE_TEMPLATE/recipe_request.yml')
-rw-r--r-- | .github/ISSUE_TEMPLATE/recipe_request.yml | 48 |
1 files changed, 48 insertions, 0 deletions
diff --git a/.github/ISSUE_TEMPLATE/recipe_request.yml b/.github/ISSUE_TEMPLATE/recipe_request.yml new file mode 100644 index 000000000..456c116bb --- /dev/null +++ b/.github/ISSUE_TEMPLATE/recipe_request.yml | |||
@@ -0,0 +1,48 @@ | |||
1 | name: Recipes - New Service Request | ||
2 | description: Suggest a service that we should add to Ferdium Recipes | ||
3 | labels: ["recipe request :sparkles:", "recipe :bookmark_tabs:"] | ||
4 | body: | ||
5 | - type: markdown | ||
6 | attributes: | ||
7 | value: | | ||
8 | Before creating a new recipe request, **please check if you can add it yourself**. | ||
9 | If you add a recipe yourself, it will be added faster than having to go through other contributors to do this job for you. | ||
10 | |||
11 | As a first option to adding a service, we recommend you search if someone already created such a recipe. For this, please search for your service name plus "Ferdium" or "Ferdi" on Github (e.g "WhatsApp Ferdium"), optionally you can also add "recipe" to the search query (e.g. "WhatsApp Ferdium recipe"). | ||
12 | If you find a recipe (e.g. https://github.com/meetfranz/recipe-whatsapp), please check that its license allows us to add it to the repository. For this, open the `package.json` file of the project and look at the specified license. In most cases this will be `"license": "MIT"`: The MIT License allows us to add the recipe! Please also check that the recipe is working (e.g. by adding it as a dev recipe to your Ferdium installation or looking if there are existing issues on the repository) and that it contains your desired features (e.g. look at the README). Another good indicator for if the recipe supports notifications is if there is code inside the `webview.js` file. | ||
13 | |||
14 | If there is no existing recipe, you can also create one yourself - this often only takes 10-20 minutes and makes it much more likely that your service will get added! To create a recipe please look at [our guide](https://github.com/ferdium/ferdium-recipes/blob/main/docs/integration.md). | ||
15 | |||
16 | **If you are not familiar with JavaScript:** Please still search for a recipe using the guide above and add it to your request. | ||
17 | - type: checkboxes | ||
18 | attributes: | ||
19 | label: Preflight Checklist | ||
20 | description: Please ensure you've completed all of the following. | ||
21 | options: | ||
22 | - label: I agree to follow the [Code of Conduct](https://github.com/ferdium/ferdium-app/blob/HEAD/CODE_OF_CONDUCT.md) that Ferdium Recipes adheres to. | ||
23 | required: true | ||
24 | - label: I have searched the [issue tracker](https://github.com/ferdium/ferdium-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22recipe+request+%3Asparkles%3A%22) for a recipe request that matches the one I want to file, without success. | ||
25 | required: true | ||
26 | - type: input | ||
27 | attributes: | ||
28 | label: Name of the service | ||
29 | description: What is the name of the service you are requesting? | ||
30 | placeholder: WhatsApp | ||
31 | validations: | ||
32 | required: true | ||
33 | - type: input | ||
34 | attributes: | ||
35 | label: URL of the service | ||
36 | description: What is the URL of the service you are requesting? | ||
37 | placeholder: https://web.whatsapp.com | ||
38 | - type: input | ||
39 | attributes: | ||
40 | label: GitHub URL to a recipe that has already been created by someone else or you | ||
41 | description: What is the URL of the service-recipe? | ||
42 | placeholder: https://github.com/... | ||
43 | - type: textarea | ||
44 | attributes: | ||
45 | label: Features you want implemented | ||
46 | description: A clear and concise description of what features you want implemented eg Notification support | ||
47 | validations: | ||
48 | required: true | ||