Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop cherry-picker tools for contributors without write permission #686

Open
1 task done
Mini256 opened this issue Aug 13, 2021 · 3 comments
Open
1 task done
Labels
lifecycle/rotten type/feature Categorizes issue or PR as related to a new feature.

Comments

@Mini256
Copy link
Member

Mini256 commented Aug 13, 2021

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

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)

@Mini256 Mini256 added the type/feature Categorizes issue or PR as related to a new feature. label Aug 13, 2021
@ti-chi-bot
Copy link
Member

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

@ti-chi-bot
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten type/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants