-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pull Request Template #1433
Comments
GitHub allows for several different types of ISSUE_TEMPLATEs, probably the same for pull requests, so we don't need to cram everything into a single template. https://blog.github.com/2018-05-02-issue-template-improvements/ via https://github.com/ffrgb/meshviewer/tree/develop/.github/ISSUE_TEMPLATE |
@mweinelt you can only add a single PR template at the moment, as far as i can see it EDIT: ok, they are possible, but not easily available to a user... |
Sure, but better start somewhere, GitHub will follow at some point. |
sure, feel free to do a pull request adding templates ;) |
Great, let's do it collaboratively: |
which problem are we addressing with these templates? |
Lack of information and structure in pull requests. Like when you add a new device you'd get the device checklist by default. The issue is that we currently can only have on PR template as it looks. |
This did not pan out, which is fine, since nobody seems to be complaining about the current state of PR descriptions. On top of that GitHub still does not support multiple PR templates and offering the device integration checklist as a default is a non-starter. |
We need a pull request template to improve on applying our guidelines and better able to track progress of pull requests.
@skorpy2009 and @rotanid wanted to take care of that. I recommend HackMD to collaborately build the text and neoraider recommended to use HTML comments to hide explanations etc..
Make use of our notes from the meeting here: https://md.darmstadt.ccc.de/gluon-device-support-policy#
The text was updated successfully, but these errors were encountered: