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 release note template to split dependency chores #5463
Add release note template to split dependency chores #5463
Conversation
Thanks @der-eismann |
28e1a43
to
80b5ba3
Compare
Done, thanks for the reminder! |
@TomSweeneyRedHat @mheon WDYT? |
We manually split the release notes up in Podman, so automating at least part of the work seems good? |
Works for me, but needs a rebase. I've been spinning a mess load of releases as of late, and it's been notably messy at best. |
80b5ba3
to
a219d36
Compare
A friendly reminder that this PR had no activity for 30 days. |
@der-eismann are you still working on this? |
a219d36
to
b443bf2
Compare
Ephemeral COPR build failed. @containers/packit-build please check. |
Yes, but I have no idea why builds fail on such a change. |
Signed-off-by: Philipp Trulson <der-eismann@users.noreply.github.com>
b443bf2
to
97d44ab
Compare
@der-eismann The build issues may be unrelated. We have been having some "fun" with our CI as of later. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: der-eismann, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
f83d266
into
containers:main
What type of PR is this?
/kind documentation
What this PR does / why we need it:
This PR adds a template to the repository to use with auto-generated release notes from GitHub. In the release notes for https://github.com/containers/buildah/releases/tag/v1.35.0 everything is put in one list, which makes it hard to differentiate actual changes from dependency updates.
This template puts the dependency updates in a separate paragraph, causing the release notes to look cleaner. This only works when PRs are labelled correctly, which is the case for renovate, but #5184 for example would need the
dependencies
label.How to verify it
Try to auto-generate release notes, but it only works after merging.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Does this PR introduce a user-facing change?