Skip to content
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

*/release-checklist: add step for merging fast-track merge requests #238

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

prestist
Copy link
Contributor

@prestist prestist commented Aug 7, 2024

After latest release we noticed fast-track pr needed a rebase due to order of pr's being merged lets instead have the person releasing the project take ownership of that responsibility.

@@ -49,6 +49,7 @@ Fedora packaging:
{%- if do_fast_track %}
- [ ] [Submit a fast-track](https://github.com/coreos/fedora-coreos-config/actions/workflows/add-override.yml) for FCOS testing-devel
- [ ] [Submit a fast-track](https://github.com/coreos/fedora-coreos-config/actions/workflows/add-override.yml) for FCOS next-devel if it is [open](https://github.com/coreos/fedora-coreos-pipeline/blob/main/next-devel/README.md)
- [ ] Approve and merge the fast-track [Pr(s)](https://github.com/coreos/fedora-coreos-config/pulls)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, sorry I misunderstood what you were suggesting. I think I'd still prefer that a second person does the code review. But the releaser should be responsible for ensuring it eventually gets merged (e.g. getting reviews or rebasing if needed).

@prestist prestist force-pushed the add-note-about-merging-fast-track branch from beb2ad1 to f1843ed Compare August 8, 2024 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants