Conversation
Contributor
|
This pull request is stale because it has been open for 60 days with no activity. |
mattdibi
force-pushed
the
ci/force-merge-bot
branch
from
566d23c to
322eb88
Compare
MMaiero
approved these changes
Mar 19, 2025
salvatore-coppola
pushed a commit
that referenced
this pull request
Mar 25, 2025
This reverts commit 3bc78e3.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a new Github workflows that allow to bypass the CI status checks via team member voting.
How it works
When a new comment is posted(or edited) in a PR, the workflow will:
/force-mergewere posted. Only repo maintainer votes will be counted (this is not a democracy) and duplicates will be discarded.It uses the new PAT introduced in eclipse-kura/.eclipsefdn#24
Possible improvements
author_associtationto grant vote rights we can create a new organization team and have that only belonging to that team will grant you voting rights. This offers more granularity and flexibility at the expense of an additional REST API call and some more admin work.