Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Ovverride the PR merge rule#513

Unanswered
PSinha1202 asked this question inQ&A
Jan 16, 2025· 2 comments· 1 reply
Discussion options

Hi Team,

Need some help or guidance in case my ask is possible.

We have a CODEOWNER file which has fileName and codeOwner Team name mapping. So when a PR gets created it pull all codeOwner teams based on files changed and the mapping. But based on default rule (correct me i am wrong) PR is not allowed to merge unless all reviewers "Approve" PR, which makes total sense.

But say sometime, changes are so small, that we might not need all approvals. So i was wondering if there is a way toenable merge Button in PR the moment we know two of codeowner has already approved it. We already have the rule setup Require approvals -- min to 1, but i think after CODEOWNER approvals is overriding it, since now it needs approval from all codeowner.

I tried few things:

ex: writing a script under .github/workflow/xyz.yml
Which basically fetches the

  1. CodeOwner list
  2. Reviewers state === 'APPROVED'
  3. Run the logic to check if we have met our two approvals from reviewers.

Question:
I am wondering if there is any API by which we can enable the PR to be merged? (enable merge Button )
If No API, then what other options we have to follow along to relax the rules of PR merge.

Any help or guidance would be much appreciated.

Regards
Prasenjit

You must be logged in to vote

Replies: 2 comments 1 reply

Comment options

I do not think there are any APIs to bypass Codeowner approval like this.

You must be logged in to vote
0 replies
Comment options

thanks@joshmgross for the input. Can you suggest or know if there are some other alternate options to the above scenario?

You must be logged in to vote
1 reply
@joshmgross
Comment options

I do not know of any alternatives

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Q&A
Labels
None yet
2 participants
@PSinha1202@joshmgross

[8]ページ先頭

©2009-2025 Movatter.jp