Enable LGTM/approval automation via GitHub actions

[elevran]

[nirrozenbaum]

#123 pre-req?

[Jooho]

Hi there! 😊
I'm looking to contribute to this task using jpmcb/prow-github-actions.

As @nirrozenbaum kindly mentioned, having an OWNERS file is a prerequisite.
Would you happen to have a list or guidance on how we should structure it?

Thanks in advance!

owners:
  - XXX

approvers:
  - XXX

reviewers:
  - XXX

[ahg-g]

perhaps follow k8s practice, see https://github.com/kubernetes-sigs/gateway-api-inference-extension/blob/main/OWNERS for GIE

[Jooho]

Yea that is the right one. please let me know who will be reviewers/approvers for this repo. I can simply send it

[elevran]

@Jooho @ahg-g
let me figure out how to get the GH org teams defined so we can reference them here (alternative: use explicit GH handles directly). Unfortunately I don't think we can use the Prow automation and infra directly.

There are slightly separate tasks:

• define CODEOWNERS (with built-in github support: limited automation, no slash command support, only owners and not reviewers, etc.).
• enable automation via GH action/bot (this would support reviewers and owners but the file format could be different than the default github format?).

Would you be able to help with finding a good automation option and creating the needed GH action flow (actions, labels, OWNERS, etc.)?
I've seen https://github.com/marketplace/actions/prow-github-actions recommended but have not found any other similar tools.
Note that it does not support GH teams - just specific GH handles.

[Jooho]

That's the one I typically used. KServe also use it. Moreover, recently I set it up for a repo(https://github.com/Jooho/loopy/blob/main/.github/workflows/prow-github.yml) and it works fine. As you said, it does not use the GH teams but it uses OWNERS file. I don't know other tools that support GH teams.

[elevran]

@Jooho based on interest and experience assigned this to you - hope that's ok.
CODEOWNERS file should be up later today so you can use that as the baseline.

[elevran]

@Jooho

• does prow-github support multiple OWNERS files so we can distribute ownership across different parts of the code? I was unable to find that in their documentation
• mergify seems to be another GH action option (for the automation, not the merge queue functionality).

[elevran]

@Jooho please let us know if you have interest and time to work on this or we should reassign 🙏

[Jooho]

@elevran I was busy :) Which one do we prefer to use? Looks like mergify is also a good option to me.