-
Notifications
You must be signed in to change notification settings - Fork 4
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
Generate changelog to release #723
Conversation
0434e55
to
0097a22
Compare
23a25ea
to
89bddc8
Compare
823cfb0
to
f3890a1
Compare
7b5caba
to
773b80d
Compare
773b80d
to
853e34e
Compare
@@ -56,6 +56,7 @@ jobs: | |||
|
|||
build_and_test_windows: | |||
runs-on: windows-2022 | |||
if: startsWith(github.ref, 'refs/tags/') && !contains(github.ref, 'swo-k8s-collector') |
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.
reverting this to original configuration as it takes ~15mins to run for every commit.
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.
"Generate release notes" button in GitHub UI still produces a bit better change log as it contains also PR refs and author, like:
- Fix service releases by @jaroslav-fedor-swi in Fix service releases #717
but it is good enough
@@ -207,6 +213,9 @@ jobs: | |||
tag_name: ${{ github.ref }} # Use the tag that triggered the workflow | |||
release_name: ${{ github.ref }} | |||
body: | | |||
**Full Changelog**: https://github.com/solarwinds/swi-k8s-opentelemetry-collector/compare/${{ env.PREVIOUS_TAG }}...${{ env.CURRENT_TAG}} | |||
## Changed |
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.
## Changed | |
## What's Changed |
We can add authors, and possibly found PR related to commit, however is that what we want? GH generate button include all changes even not related to the release. It works well if you have single purpose repo. |
Find all commits in given PATH between two tags, and add it as release notes into release.
Image:
data source:
Helm