-
Notifications
You must be signed in to change notification settings - Fork 296
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
[repo] Release request issue template & automation #2080
[repo] Release request issue template & automation #2080
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2080 +/- ##
==========================================
- Coverage 73.91% 70.07% -3.85%
==========================================
Files 267 332 +65
Lines 9615 12942 +3327
==========================================
+ Hits 7107 9069 +1962
- Misses 2508 3873 +1365 Flags with carried forward coverage won't be shown. Click here to find out more. |
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.
Great improvement!
Test failures from SQL seem unrelated, merged. See: #2086 |
Changes
Details
We have a prepare-release workflow with a dispatch trigger which can be used to automate component releases out of this repo. The challenge is only writers/approvers and admins/maintainers can kick that off. Owners of components who do not have at least writer permission cannot use the automation.
What this PR does is add an issue template for requesting a release because... everyone can create issues!
If a release request is opened by an approver/writer or maintainer/admin, the bot will automatically kick off the prepare release workflow.
If a release request is opened for a component by a user who is listed as an owner of that component in component_owners.yml, the bot will automatically kick off the release workflow.
If a release request is opened by a random user, the bot will tag component owners, approvers/writer, and maintainers/admins who may "approve" the process by using a command ("/PrepareRelease").
Here are some test runs:
A release request opened by a random user and being approved by a component owner: [release request] OneCollector 1.10.0-rc.1 CodeBlanchOrg/opentelemetry-dotnet-contrib#42
A release request being opened by a component owner: [release request] OneCollector 1.10.0-rc.2 CodeBlanchOrg/opentelemetry-dotnet-contrib#44
Testing invalid inputs: [release request] negative tests CodeBlanchOrg/opentelemetry-dotnet-contrib#46
Note: Need to update RELEASING.md with instructions but I'll do that as a follow-up.
Merge requirement checklist