Add GitHub Issue Templates #3264
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For: - Bug Reports - Feature Requests - New Releases Mostly this was a way to document our release process and capture it in issues, similar to other Azavea OSS projects. Bonus that we can begin iterating on a few other common issue template types.
pomadchin
requested changes
Jun 23, 2020
I can do that, or we can also use this feature to add a link to the gitter channel to direct users with questions there from the issue creation screen. Do you have a preference? |
|
@CloudNiner oh, I don't know how would it look like; if it is not convenient, why not? 👍 |
|
Created config.yml with Gitter link instead of adding another issue template. Kept the ability for users to open blank issues because there's definitely issue categories we aren't accounting for. |
pomadchin
approved these changes
Jun 24, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For:
Mostly this was a way to document our release process and capture
it in issues, similar to other Azavea OSS projects, until we are able to
address #3140
Bonus that we can begin iterating on a few other common issue
template types.
@pomadchin pay particular attention to the steps in the new release.md issue template. Please double-check that I didn't miss any of the key release steps.