eclipse-score / eclipse-score/score
PR approval gating by multiple groups in S-CORE
- Dominant language
- Starlark
- Stars
- 109
- Forks
- 105
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 24
Description
Description:
---------------
We need to analyze whether it is possible to enforce PR approval rules in S-CORE that require approvals from multiple groups before merging.
Context
---------
Currently, GitHub allows us to require a minimum number of reviewers for a PR. However, this does not ensure that approvals come from distinct groups/roles (e.g., architecture community, team leads, committers).
Example requirement:
-------------------------
A merge into the feature section of S-CORE should require at least one approval from @team_a and two approvals from @team_b.
The rule must work as an AND conjunction not OR (i.e., at least one representative of both groups must approve).
Considerations
------------------
- Must align with S-CORE governance roles (Committers vs Contributors).
- Integrate with existing CODEOWNERS rules if possible.
- Explore whether this can be achieved via:
- Native GitHub branch protection rules.
- A bot or GitHub Action that enforces multi-group approval.
- External tooling or custom automation.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.