-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[docs] update pull request template to ask contributors to write unit tests #21427
Merged
Merged
Changes from all commits
Commits
Show all changes
2 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,22 +1,26 @@ | ||
<!-- Thanks for contributing to _fastlane_! Before you submit your pull request, please make sure to check the following boxes by putting an x in the [ ] (don't: [x ], [ x], do: [x]) --> | ||
|
||
### Checklist | ||
|
||
- [ ] I've run `bundle exec rspec` from the root directory to see all new and existing tests pass | ||
- [ ] I've followed the _fastlane_ code style and run `bundle exec rubocop -a` to ensure the code style is valid | ||
- [ ] I see several green `ci/circleci` builds in the "All checks have passed" section of my PR ([connect CircleCI to GitHub](https://support.circleci.com/hc/en-us/articles/360008097173-Why-aren-t-pull-requests-triggering-jobs-on-my-organization-) if not) | ||
- [ ] I've read the [Contribution Guidelines](https://github.com/fastlane/fastlane/blob/master/CONTRIBUTING.md) | ||
- [ ] I've updated the documentation if necessary. | ||
- [ ] I've added or updated relevant unit tests. | ||
|
||
### Motivation and Context | ||
|
||
<!-- Why is this change required? What problem does it solve? --> | ||
<!-- If it fixes an open issue, please link to the issue following this format: | ||
Resolves #999999 | ||
--> | ||
|
||
### Description | ||
<!-- Describe your changes in detail. --> | ||
<!-- Please describe in detail how you tested your changes. --> | ||
|
||
<!-- Describe your changes in detail, as well as how you tested them. --> | ||
|
||
### Testing Steps | ||
|
||
<!-- Optional: steps, commands, or code used to test your changes. --> | ||
<!-- Providing these will reduce the time needed for testing and review by the fastlane team. --> |
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.
I added these line breaks as it's a markdown good practice to surround headers with line breaks (before and after), as some markdown interpreters don't parse them correctly when there are no line breaks after headers