-
Notifications
You must be signed in to change notification settings - Fork 144
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
Setup CODEOWNERS #1669
Setup CODEOWNERS #1669
Conversation
TODO before this could be merged:
#!/bin/bash
set -o errexit -o nounset -o pipefail
export owners_alias=$1
gh_team=$2
owners=$(yq < OWNERS_ALIASES '.aliases[strenv(owners_alias)][]' | sort -u)
members=$(gh api orgs/konflux-ci/teams/"$gh_team"/members --jq '.[].login' | sort)
diff --color <(echo "$owners") <(echo "$members")
And the |
Changed the CODEOWNERS based on #1658 Addressed the OWNERS_ALIASES vs. GH team mismatches
|
/retest |
Need to add one more thing - Renovate groupings based on CODEOWNERS. Otherwise Renovate PRs will need approvals from many different sets of owners |
CC @acornett21 @amisstea @arewm @avi-biton @bcrochet @brianwcook @brunoapimentel @cgwalters @eskultety @gbenhaim @gurnben @hmariset @jbpratt @kdudka @komish @ligangty @oamsalem @Omeramsc @ralphbean @scoheb @skattoju @taylormadore @yftacherzog @yma96 This PR adds you as a CODEOWNER (because you were already in an OWNERS file), which means you'll now have the power to self-service changes to your tasks. On the other hand, it means your approval will be required in order for those changes to be merged. Let me know if you have any concerns about that. |
/test |
Btw, the Renovate groupings based on filenames seem to work well. See for example chmeliik#45, chmeliik#46, which both update the oras image, but in two separate PRs according to the matchFileNames groupings |
Added |
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.
🌮
Signed-off-by: Adam Cmiel <acmiel@redhat.com>
CODEOWNERS will allow us to make the ownership of individual tasks actually mean something. We will have to give every owner write permissions, but we will be able to set up branch protection rules to block PRs from getting merged if they don't have approvals from the owners. This will allow the CODEOWNERS of tasks and stepactions to fully self-service their PRs without giving them the ability to mess with other parts of the repository. The file was generated based on the current **/OWNERS Signed-off-by: Adam Cmiel <acmiel@redhat.com>
Signed-off-by: Adam Cmiel <acmiel@redhat.com>
Signed-off-by: Adam Cmiel <acmiel@redhat.com>
And a python script to update renovate.json based on those directives. Signed-off-by: Adam Cmiel <acmiel@redhat.com>
Align to 2-space indentation everywhere because we'll be making automated changes to the file. Signed-off-by: Adam Cmiel <acmiel@redhat.com>
Signed-off-by: Adam Cmiel <acmiel@redhat.com>
They will be assigned based on CODEOWNERS Signed-off-by: Adam Cmiel <acmiel@redhat.com>
Make sure the groups will stay up to date with CODEOWNERS Signed-off-by: Adam Cmiel <acmiel@redhat.com>
/retest |
There hasn't been pushback to this approach (or the pushback has been resolved). The CODEOWNERS file is now fully valid. Merging |
CODEOWNERS will allow us to make the ownership of individual tasks
actually mean something.
We will have to give every owner write permissions, but we will be able
to set up branch protection rules to block PRs from getting merged if
they don't have approvals from the owners.
This will allow the CODEOWNERS of tasks and stepactions to fully
self-service their PRs without giving them the ability to mess with
other parts of the repository.