-
Notifications
You must be signed in to change notification settings - Fork 97
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
Add a PR Checklist for Contributions #7921
Conversation
.github/pull_request_template.md
Outdated
Please verify that the PR meets the following requirements, where applicable: | ||
|
||
- [ ] An overview of proposed schema changes is included in a linked GitHub issue. | ||
- [ ] A design document PR is created in the [design-notes repository](https://github.com/radius-project/design-notes/), if new APIs are being introduced. | ||
- [ ] A PR for the [samples repository](https://github.com/radius-project/samples) is created, if existing samples are affected by the changes in this PR. | ||
- [ ] A PR for the [documentation repository](https://github.com/radius-project/docs) is created, if the changes in this PR affect the documentation. |
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 an initial draft. Please feel free to suggest updates to the list/phrasing etc.
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.
Should we talk about tests like adding unit and functional tests?
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 like the idea of adding functional tests in the checklist, but hesitant to add it until we build a consensus with the team on it. Mainly because it existed in the old checklist and was removed due to being ignored. @rynowak, do you have strong opinions on this?
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7921 +/- ##
==========================================
- Coverage 60.64% 60.63% -0.02%
==========================================
Files 534 534
Lines 28488 28488
==========================================
- Hits 17277 17273 -4
- Misses 9698 9700 +2
- Partials 1513 1515 +2 ☔ View full report in Codecov by Sentry. |
- [ ] An overview of proposed schema changes is included in a linked GitHub issue. | ||
- [ ] A design document PR is created in the [design-notes repository](https://github.com/radius-project/design-notes/), if new APIs are being introduced. |
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.
should we combine these? they either update the GH issue with the details on the schema changes or they do a design doc if it involves new API 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.
Could you suggest the user facing phrasing you have on mind for combining these? @Reshrahim
|
||
- [ ] An overview of proposed schema changes is included in a linked GitHub issue. | ||
- [ ] A design document PR is created in the [design-notes repository](https://github.com/radius-project/design-notes/), if new APIs are being introduced. | ||
- [ ] A PR for the [samples repository](https://github.com/radius-project/samples) is created, if existing samples are affected by the changes in this PR. |
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.
do we want to include more possibilities so we , say, 'add new samples when new features are introduced'.
One suggestion:
..ensure samples repo adequately addresses changes in this PR (which may include addition/update/deletion) of samples
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 a new sample needs to be added, then that should be covered in the design review discussion (# 2), we can expand that to new API/significant feature to be explicit, if that helps. This list captures what we agreed on in the team meeting.
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.
Should we include design reviews? Is this template just for creating a PR or should it cover the review and approval process as well. It would give contributors a clear idea of the path to accepting the PR.
Thanks for the review, @superbeeny. Do you mean expanding this checklist item to explicitly to call out review + approval of the design doc?
|
Yes, it gives contributors immediate visibility into the status of the PR |
That makes sense, I'll update it. |
31f41c7
to
771ac88
Compare
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
c06a86b
to
250aae7
Compare
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Signed-off-by: karishma-chawla <[email protected]>
Signed-off-by: karishma-chawla <[email protected]>
Signed-off-by: karishma-chawla <[email protected]>
Signed-off-by: karishma-chawla <[email protected]>
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Description
Adding a contribution PR checklist to ensure important areas like, design, samples, and doc updates are covered.
Type of change