-
Notifications
You must be signed in to change notification settings - Fork 118
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
Add issue and pull request templates to all code repositories #138
Labels
infrastructure
Requires changes on the web server or other infra
Comments
chapulina
added
the
infrastructure
Requires changes on the web server or other infra
label
Feb 3, 2021
This was referenced Feb 5, 2021
This was referenced Feb 5, 2021
Some things to update on the second pass:
|
All done! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Templates help contributors ticket more straightforward issues and pull requests. We should add them to all our code repositories.
How
Here's some GitHub documentation about it:
https://docs.github.com/en/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository
I added some rough examples to the testing repository, see all the
TEMPLATE
s:https:/ignitionrobotics/testing/tree/main/.github
The two options show up when ticketing an issue:
https:/ignitionrobotics/testing/issues/new/choose
Opening a PR uses the default pull request template (the one outside the folder):
gazebosim/testing@main...another_branch
And the other PR templates can be accessed using the
?template=
query (unfortunately, not through the UI yet):Unfortunately, it looks like the automated title and labels aren't working for PR templates 😕
Content
We should have 2 issue templates: bugs and features, and 3 PR templates: bugs, features and ports.
There are lots of nice guides online for what to include in these templates. I'll brainstorm some ideas below and mention some Ignition-specific things.
Issues
Bug
Feature
PRs
Bug
Feature
Ports
The text was updated successfully, but these errors were encountered: