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
Update PR Template #4183
Update PR Template #4183
Conversation
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.
Approved -- a few minor suggestions. I suggest asking other people on the team to also review this, and post in our Slack channel, so people are aware of this change (and can weigh in if need-be).
Co-Authored-By: dobooth <dobooth@adobe.com>
Co-Authored-By: dobooth <dobooth@adobe.com>
Co-Authored-By: dobooth <dobooth@adobe.com>
.github/CONTRIBUTING.md
Outdated
|
||
Create a PR to the [magento/devdocs repo](https://github.com/magento/devdocs). Fill out as much info as possible and link any GitHub issues. | ||
|
||
In general, you should use `master` as the base branch when creating a PR. If your contribution is related to a release that is in progress, use a version-specific integration branch, like `2.3.1-integration`. |
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.
develop
is a release integration branch.
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.
Seems like we should change this when we officially make the repo changes.
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.
We've been using the develop branch officially:
https://github.com/magento/devdocs/tree/develop
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.
Done.
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.
There is an ambiguity that makes use of these types confusing along with labels.
Too many entities for a PR type specification.
It would make sense to use here the same options that we use for labels:
- New topic
- Major update
- Technical
- Editorial
- Site improvements
- Bug
Co-Authored-By: dobooth <dobooth@adobe.com>
Co-Authored-By: dobooth <dobooth@adobe.com>
Co-Authored-By: dobooth <dobooth@adobe.com>
.github/PULL_REQUEST_TEMPLATE.md
Outdated
- [ ] Content update | ||
- [ ] Content fix or rewrite | ||
- [ ] Bug fix or improvement | ||
Describe the goal and the types of changes this PR covers. |
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.
Describe the goal and the types of changes this PR covers. | |
Describe the goal and the type of changes this PR covers. |
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.
Add a list of types.
It should correspond to the labels we use. The labels already contain short descriptions, so you could just copy the label description.
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.
Good idea.
.github/PULL_REQUEST_TEMPLATE.md
Outdated
## Additional information | ||
|
||
List all affected URLs | ||
List all files that this PR changes: |
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.
The list of files is always available in the GitHub UI at Files changed tab
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.
This is nice to have up front for editors, groomers...
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.
.github/PULL_REQUEST_TEMPLATE.md
Outdated
|
||
<!-- | ||
Thank you for your contribution! | ||
If this PR references a file in a Magento repository, add it here. |
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.
If this PR references a file in a Magento repository, add it here. | |
If this PR references a file in a Magento codebase repository, add it here. |
.github/PULL_REQUEST_TEMPLATE.md
Outdated
<!-- (REQUIRED) The Url that this PR will modify --> | ||
|
||
<!-- (OPTIONAL) What other information can you provide about this PR? --> | ||
## Source code URLS (remove if unused) |
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.
## Source code URLS (remove if unused) | |
## Links to source code (remove if unused) |
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.
Done.
Co-Authored-By: dobooth <dobooth@adobe.com>
Co-Authored-By: dobooth <dobooth@adobe.com>
Co-Authored-By: dobooth <dobooth@adobe.com>
Co-Authored-By: dobooth <dobooth@adobe.com>
.github/PULL_REQUEST_TEMPLATE.md
Outdated
|
||
## Additional information | ||
## Affected URLS (required) |
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.
Change to URLs
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.
Done.
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.
Tossed in some comments.
.github/PULL_REQUEST_TEMPLATE.md
Outdated
- [ ] Content fix or rewrite | ||
- [ ] Bug fix or improvement | ||
We set labels (and therefore points) based on the scope of changes with a PR. | ||
Note the scope of this PR by leaving one of the options below and deleting the others. |
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.
Maybe move this line before the labels one to call for action?
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.
Done.
Co-Authored-By: dobooth <dobooth@adobe.com>
Co-Authored-By: dobooth <dobooth@adobe.com>
Impressed with the feedback! Good job! :) |
.github/PULL_REQUEST_TEMPLATE.md
Outdated
|
||
Feel free to remove this section before creating this PR. | ||
`master` is the default branch. Be sure to change the base if your PR is for another branch. |
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'd like an explanation of what master means to us, and when to use develop or some other branch.
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.
Done.
running tests |
Hi @dobooth, thank you for your contribution! |
This PR is a:
Summary
When this pull request is merged, it will...
Update the PR template to remove checkboxes and align contribution types to label.
Add a section about selecting a contribution type when submitting a PR.
https://github.com/magento/devdocs/blob/master/.github/CONTRIBUTING.md