Added: templates #1
Conversation
| * Browser Name and version: | ||
| * Operating System and version (desktop or mobile): | ||
| * Link to your project: |
There was a problem hiding this comment.
At least for wg-access-server these three never mattered for us in any of the existing issues.
Instead we could ask for config files or relevant parts of them, like the config.yaml or docker-compose.yml.
| @@ -0,0 +1,20 @@ | |||
| <!--- Use a prefix like [TASK], [BUGFIX], [DOC] or [CGL] and provide a general summary of your changes in the Title above --> | |||
There was a problem hiding this comment.
We didn't use such prefixes until now and I'm not too big of a fan of them. I'd short the sentence to simply
<!--- Provide a general summary of your changes in the Title above -->
| <!--- If it fixes an open issue, please link to the issue here. --> | ||
|
|
||
| ## How Has This Been Tested? | ||
| <!--- Please try to test the code in multiple browsers and also on a mobile device --> |
There was a problem hiding this comment.
Similar to the "Your environment" section above, this often doesn't make sense, e.g. if the PR only touches backend code. Maybe it could be made a bit more generic?
<!--- Please try to test the code in multiple situations and with different settings that could influence it -->
| ## Checklist: | ||
| <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> | ||
| <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> | ||
| - [ ] My code follows the code style of this project. (CI will test it anyway and also needs approval) |
There was a problem hiding this comment.
For wg-access-server it would be useful to point people towards go fmt, Go's built-in formatter. But that's very project-/language-specific, so it doesn't fit here I guess.
I've added PR & Issue templates as well as a README file
Closes freifunkMUC/wg-access-server#74