Skip to content

Conversation

joestringer
Copy link
Member

@joestringer joestringer commented May 2, 2024

Assign a couple of extra files to release-managers since they are
commonly modified while preparing a release.

cc @cilium/release-managers

@joestringer joestringer requested a review from a team as a code owner May 2, 2024 21:44
@joestringer joestringer added the release-note/misc This PR makes changes that have no direct user impact. label May 2, 2024
@joestringer joestringer requested a review from aditighag May 2, 2024 21:44
@joestringer joestringer marked this pull request as draft May 3, 2024 17:29
Copy link

github-actions bot commented Jun 3, 2024

This pull request has been automatically marked as stale because it
has not had recent activity. It will be closed if no further activity
occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale. label Jun 3, 2024
Copy link

This pull request has not seen any activity since it was marked stale.
Closing.

@github-actions github-actions bot closed this Jun 17, 2024
@joestringer joestringer reopened this Jul 16, 2025
Assign a couple of extra files to release-managers since they are
commonly modified while preparing a release.

Signed-off-by: Joe Stringer <joe@cilium.io>
@joestringer joestringer force-pushed the pr/joe/release-codeowners branch from 264e44f to 0f488ad Compare July 16, 2025 00:21
@joestringer
Copy link
Member Author

/test

@joestringer joestringer marked this pull request as ready for review July 16, 2025 00:22
@joestringer joestringer requested review from a team as code owners July 16, 2025 00:22
@joestringer joestringer enabled auto-merge July 16, 2025 00:22
@joestringer joestringer removed the stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale. label Jul 16, 2025
@qmonnet qmonnet removed the request for review from aditighag July 16, 2025 09:34
@qmonnet
Copy link
Member

qmonnet commented Jul 16, 2025

I wish there was a way to make the distinction between release-related PRs, and other regular changes to the README.rst, to pull the right team accordingly. But I don't see any simple way to do that 😕

@joestringer joestringer added this pull request to the merge queue Jul 16, 2025
Merged via the queue into main with commit 4201802 Jul 16, 2025
74 checks passed
@joestringer joestringer deleted the pr/joe/release-codeowners branch July 16, 2025 09:45
@maintainer-s-little-helper maintainer-s-little-helper bot added ready-to-merge This PR has passed all tests and received consensus from code owners to merge. labels Jul 16, 2025
@maintainer-s-little-helper maintainer-s-little-helper bot added ready-to-merge This PR has passed all tests and received consensus from code owners to merge. labels Jul 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants