Create a shared OWNERS vs internal-acls validation
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 61
- Forks
- 91
- Avg merge
- 12d 10h
- Merged PRs (30d)
- 1
Description
The goal of this issue is to create a composite action with owners-file and team inputs, supporting multiple OWNERS files per repo.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names a composite action with owners-file and team inputs, but no files or tests. Start by locating the repository's existing OWNERS/internal-acls validation entry point and related action definitions; done means one shared action supports multiple OWNERS files per repository and validates the supplied teams.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100