-
Notifications
You must be signed in to change notification settings - Fork 11.7k
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
feat: update pr templates, closes #696 #699
Merged
frangio
merged 4 commits into
OpenZeppelin:master
from
shrugs:feat/reorg-templates-#696
Jan 25, 2018
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,17 +1,17 @@ | ||
<!-- π Thank you for submitting a PR! Before submitting, please review the following checklist: --> | ||
<!-- 0. π Thank you for submitting a PR! --> | ||
|
||
- [ ] π I've reviewed the [OpenZeppelin Contributor Guidelines](/docs/CONTRIBUTING.md) | ||
- [ ] β I've added tests where applicable to test my new functionality. | ||
- [ ] π I've made sure that my contracts are well-documented. | ||
- [ ] π¨ I've run the JS/Solidity linters (`npm run lint:all:fix`) and fixed any issues. | ||
|
||
<!-- **Does this close any open issues?** If so, list them here. --> | ||
<!-- 1. **Does this close any open issues?** If so, list them here. If not, remove the `Fixes #` line. --> | ||
|
||
Fixes # | ||
|
||
--- | ||
|
||
# π Description | ||
|
||
<!-- Describe the changes introduced in this pull request --> | ||
<!-- Include any context necessary for understanding the PR's purpose. --> | ||
<!-- 2. Describe the changes introduced in this pull request --> | ||
<!-- Include any context necessary for understanding the PR's purpose. --> | ||
|
||
<!-- 3. Before submitting, please review the following checklist: --> | ||
|
||
- [ ] π I've reviewed the [OpenZeppelin Contributor Guidelines](/docs/CONTRIBUTING.md) | ||
- [ ] β I've added tests where applicable to test my new functionality. | ||
- [ ] π I've made sure that my contracts are well-documented. | ||
- [ ] π¨ I've run the JS/Solidity linters (`npm run lint:all:fix`) and fixed any issues. | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While we're at it, I'd move the command in parentheses to the end of the sentence, after "fixed any issues".