Update the Pull Request template#2
Merged
Merged
Conversation
Added Documentation section and PR Guidelines at the bottom
RohitRox
approved these changes
May 19, 2020
josisusan
approved these changes
May 19, 2020
milap-neupane
approved these changes
May 19, 2020
milap-neupane
approved these changes
May 19, 2020
|
Isn't this file and the file inside |
Contributor
Author
|
@anaida07 Need to check which one is taken as source. We can manage then. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Component Name:
Organization Level governance for default Pull Request template
Summary/Motivation:
Updated the default Pull Request template with few formatting changes and also added a Documentation section as a reminder for developers.
If a repo does not have a PR template then this default template will kick into action. If we all can agree then, we can do without the repo level template and use this global template, unless we require something specific.
Deployment Strategy:
Merging will make this auto available across all the repositories.