-
Notifications
You must be signed in to change notification settings - Fork 3.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
Update PR template for release process #2041
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #2041 +/- ##
========================================
Coverage 64.86% 64.86%
========================================
Files 115 115
Lines 6862 6862
========================================
Hits 4451 4451
Misses 2127 2127
Partials 284 284 |
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 think this is too verbose to add into the PR template (4 lines for one concept is a lot) - I think this should instead be added to CONTRIBUTING.md
. Maybe having just the first line Targeted PR against correct branch
and have it linked to the section in CONTRIBUTING
could make sense
OK; so updated. |
.github/PULL_REQUEST_TEMPLATE.md
Outdated
@@ -4,6 +4,11 @@ v Before smashing the submit button please review the checkboxes. | |||
v If a checkbox is n/a - please still include it but + a little note why | |||
☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --> | |||
|
|||
- Targeted PR against correct branch: | |||
- `release/vxx.yy.zz` for a merge into a release candidate |
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 we're going to list this in the pr template we should give more direction as to what prs go into the release. If we don't, then this shouldn't go in the template imo
### PR Targeting | ||
|
||
Ensure that you base and target your PR on the correct branch: | ||
- `release/vxx.yy.zz` for a merge into a release candidate |
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 we're going to list this in the CONTRIBUTING.md we should give more direction as to what prs go into the release. Right now this basically just states what the main branches are, not which PR's should go where.
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.
Added a paragraph to explain which PRs should go where.
* Upgrade to v9 * Update handler * Fix linter * Remove old or basic upgrades from codecov * add execute rights to test scripts (cosmos#2041) * Add e2e tests * Update code smell * Remove and refactor duplicated query exec * Fix linter * Update ICS dependency * Update dependency * Fix typo Co-authored-by: Simon Noetzlin <[email protected]> Co-authored-by: MSalopek <[email protected]> Co-authored-by: Simon Noetzlin <[email protected]>
For Admin Use: