[NO-JIRA] Allow approvers from OWNERS file to run sync gha

[atheo89]

This upgrade allow approvers from OWNERS file to run sync gha

Description

How Has This Been Tested?

https://github.com/atheo89/test-auth-users/actions/runs/11382115618/job/31664947802#step:3:23

Merge criteria:

• The commits are squashed in a cohesive manner and have meaningful messages.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from atheo89. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jiridanek]

Wow, thanks for the thought!

I can't trigger the GHA with the button on https://github.com/opendatahub-io/kubeflow/actions/workflows/sync-branches-through-pr.yaml

How does the PR help with that?

[jiridanek]

Furthermore, if the https://github.com/opendatahub-io/kubeflow/actions/workflows/notebook-controller-images-updater.yaml action ran before on both main and v1.9-branch, then there will always be a merge conflict and the sync action will not finish cleanly.

But that's something that can be resolved by adding few sed commands to

kubeflow/.github/workflows/sync-branches-through-pr.yaml

Line 27 in c3d9c8b

- name: Prepare sync branch

so that's not a problem for now.

[atheo89]

I can't trigger the GHA with the button on

🤦‍♀️ no idea.
FYI if you add people as collaborators, you can hit that button. Now in this case you are in a team that is called Notebook Devs. I guessed that you have the super power to hit that button.. Maybe we need to dive into the settings.

action ran before on both main and v1.9-branch, then there will always be a merge conflict and the sync action will not finish cleanly.

That is true, we should care also

[jiridanek]

Still no powers, as far as I can see.

If I understand this PR correctly, I'd title it "Prevent people not in OWNERS file to run sync gha"; it's not about giving access, but about restricting access, looks to me

[atheo89]

This won't work since the Notebook Devs team has triage rights, for this actions needs write.
Closing this, maybe we will found another way.