This repository has been archived by the owner on Nov 27, 2022. It is now read-only.
GitHub templates #5
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
|
😲 Did you just adhere to your own template? 😄 Great job, will add this before the v1.0.0 release this weekend. |
|
These templates will make the PR descriptions very useful when it comes to creating release notes and managing releases. Great job @m14t |
RubenVerborgh
force-pushed
the
feature/github-templates
branch
2 times, most recently
from
1bcb35e
to
2d09ef3
Compare
RubenVerborgh
force-pushed
the
feature/github-templates
branch
from
2d09ef3
to
e8f816d
Compare
|
Thanks a lot! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What kind of change does this PR introduce?
What does this PR do?
This PR adds both a Pull Request Template, and a template for both bug fixes and feature requests using multiple template types.
Links to relevant issues:
Does this PR introduce a breaking change?
The PR fulfills these requirements:
All tests are passingN/ANew/updated tests are includedN/AOther information:
Once this PR is merged, when a user clicks on "New Issue" they will be directed to https://github.com/solid/react-components/issues/new/choose, which will display a screen like: