-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Allow to cherry-pick commit to other branch #3880
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
I think it would be great. Since this would be automatic, Gitea can not only sign the new PR but also certify that it's an actual cherry-pick of the original PR. |
Is there a way to help (financially) to accelerate this? I would be glad to contribute. |
Sorry, I don't know. The number of money is not equal to the value of the feature. How much do you want to donate depends on yourself. |
Well, a donation is one thing and asking someone (a budget) to develop something is another thing. I guess both are welcome in this (and any) opensource project, but I'm trying to find out more about the second option, where money equals the time of the developer (kind of). |
This code adds a simple endpoint to apply patches to repositories and branches on gitea. This is then used along with the conflicting checking code in #18004 to provide a basic implementation of cherry-pick revert. Now because the buttons necessary for cherry-pick and revert have required us to create a dropdown next to the Browse Source button I've also implemented Create Branch and Create Tag operations. Fix #3880 Fix #17986 Signed-off-by: Andrew Thornton <art27@cantab.net>
…#17902) This code adds a simple endpoint to apply patches to repositories and branches on gitea. This is then used along with the conflicting checking code in go-gitea#18004 to provide a basic implementation of cherry-pick revert. Now because the buttons necessary for cherry-pick and revert have required us to create a dropdown next to the Browse Source button I've also implemented Create Branch and Create Tag operations. Fix go-gitea#3880 Fix go-gitea#17986 Signed-off-by: Andrew Thornton <art27@cantab.net>
It would allow to backport commits to other branches more easily from UI. Of course that would work only for commits that does not have conflicts with target branch
The text was updated successfully, but these errors were encountered: