You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the past, we launched a new cherry-picker tool to help contributors cherry-pick PR on the master branch to the related release branch, the robot will automatically submit a new PR.
However, when the code in the PR conflicts, this will require manual conflict resolution, the robot allows members with write permission in the repository to modify the submitted PR through the Allow edited by maintainer option.
For security reasons, we will no longer automatically add write permissions to the robot warehouse for the contributor.
But this brings a lot of trouble to contributors who don’t have permission. They don’t have permission to submit code for resolution when PR code conflicts.
Therefore, we need to develop a cherrypicker-like script to allow the contributor to quickly and easily pick the merged PR to the relevant release branch through simple interaction.
Do you have any ideas on how to implement it? (Optional)
The text was updated successfully, but these errors were encountered:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle rotten
Feature Request
Is your feature request related to an Issue or PR(Optional)
Describe the feature you'd like:
In the past, we launched a new cherry-picker tool to help contributors cherry-pick PR on the master branch to the related release branch, the robot will automatically submit a new PR.
However, when the code in the PR conflicts, this will require manual conflict resolution, the robot allows members with write permission in the repository to modify the submitted PR through the Allow edited by maintainer option.
For security reasons, we will no longer automatically add write permissions to the robot warehouse for the contributor.
But this brings a lot of trouble to contributors who don’t have permission. They don’t have permission to submit code for resolution when PR code conflicts.
Therefore, we need to develop a cherrypicker-like script to allow the contributor to quickly and easily pick the merged PR to the relevant release branch through simple interaction.
Do you have any ideas on how to implement it? (Optional)
The text was updated successfully, but these errors were encountered: