-
Notifications
You must be signed in to change notification settings - Fork 15
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
Improve accuracy and detail of release notes #3103
Closed
2 tasks done
Labels
Streamline eCR
Issues for Streamline eCR team to work on
Comments
austin-hall-skylight
added
the
Streamline eCR
Issues for Streamline eCR team to work on
label
Jan 6, 2025
3 tasks
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 23, 2025
Loading
Loading status checks…
# PULL REQUEST ## Summary - Update release action to auto generate release notes - [Tag will get created if it does not exist](https://cli.github.com/manual/gh_release_create#:~:text=If%20a%20matching%20git%20tag%20does%20not%20yet%20exist%2C%20one%20will%20automatically%20get%20created%20from%20the%20latest%20state%20of%20the%20default%20branch.) - [Title will automatically be created based on the tag](https://cli.github.com/manual/gh_release_create#:~:text=When%20using%20automatically%20generated%20release%20notes%2C%20a%20release%20title%20will%20also%20be%20automatically%20generated%20unless%20a%20title%20was%20explicitly%20passed.%20Additional%20release%20notes%20can%20be%20prepended%20to%20automatically%20generated%20notes%20by%20using%20the%20%2D%2Dnotes%20flag.) ## Related Issue Fixes #3103 ## Acceptance Criteria - [x] Release notes contain the title and description for each merged pull request included in the release - [x] Pull requests that have been closed but not merged are not included in the release notes ## Additional Information Example of what `gh release create 0.0.2 --generate-notes` will create: ![image](https://github.com/user-attachments/assets/d41ce1d8-bf95-4dab-a096-b8785969447c) ## Checklist - [ ] If this code affects the other scrum team, have they been notified? (In Slack, as reviewers, etc.) [//]: # "PR title: Remember to name your PR descriptively!"
robertmitchellv
pushed a commit
that referenced
this issue
Jan 23, 2025
Loading
Loading status checks…
# PULL REQUEST ## Summary - Update release action to auto generate release notes - [Tag will get created if it does not exist](https://cli.github.com/manual/gh_release_create#:~:text=If%20a%20matching%20git%20tag%20does%20not%20yet%20exist%2C%20one%20will%20automatically%20get%20created%20from%20the%20latest%20state%20of%20the%20default%20branch.) - [Title will automatically be created based on the tag](https://cli.github.com/manual/gh_release_create#:~:text=When%20using%20automatically%20generated%20release%20notes%2C%20a%20release%20title%20will%20also%20be%20automatically%20generated%20unless%20a%20title%20was%20explicitly%20passed.%20Additional%20release%20notes%20can%20be%20prepended%20to%20automatically%20generated%20notes%20by%20using%20the%20%2D%2Dnotes%20flag.) ## Related Issue Fixes #3103 ## Acceptance Criteria - [x] Release notes contain the title and description for each merged pull request included in the release - [x] Pull requests that have been closed but not merged are not included in the release notes ## Additional Information Example of what `gh release create 0.0.2 --generate-notes` will create: ![image](https://github.com/user-attachments/assets/d41ce1d8-bf95-4dab-a096-b8785969447c) ## Checklist - [ ] If this code affects the other scrum team, have they been notified? (In Slack, as reviewers, etc.) [//]: # "PR title: Remember to name your PR descriptively!"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What needs to be done
Why it needs to be done
Release notes currently include PR's that have been closed but not merged. This will fix that error as well as giving us more detailed information about each PR that is included in the release.
Acceptance Criteria
Technical Notes
Additional context
n/a
The text was updated successfully, but these errors were encountered: