Skip to content

[Feature request] Reverting a pull request #6375

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

Open
ghost opened this issue Mar 19, 2019 · 13 comments
Open

[Feature request] Reverting a pull request #6375

ghost opened this issue Mar 19, 2019 · 13 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented issue/workaround it is or has a workaround type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@ghost
Copy link

ghost commented Mar 19, 2019

Please consider adding a feature to revert pull requests, just like on github: https://help.github.com/en/articles/reverting-a-pull-request

@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Mar 20, 2019
@lunny lunny added this to the 1.x.x milestone Mar 20, 2019
@stale
Copy link

stale bot commented May 19, 2019

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.

@stale stale bot added the issue/stale label May 19, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label May 19, 2019
@stale stale bot removed the issue/stale label May 19, 2019
@6543
Copy link
Member

6543 commented Oct 9, 2019

can we add this to v1.11.x ?

because it sounds very usefull and we dont loose track of it

@lunny
Copy link
Member

lunny commented Nov 2, 2019

@6543 but nobody are working on this even I think it's not difficult to implement.

@su-tiko
Copy link

su-tiko commented Aug 31, 2020

Is there any plan to implement this feature? Thanks.

@6543
Copy link
Member

6543 commented Aug 31, 2020

@vjgarcera plan: well issue is till open ;)

But no dev has picked it jet, feel free to have a look

@wxiaoguang
Copy link
Contributor

A commit could be reverted on the web UI, so reverting the PR's commit could revert that PR:

image

@lunny
Copy link
Member

lunny commented Dec 15, 2024

Yes, so we just need a button in the merged Pull Request View which can be linked to the same URL. It should not be a very big change from current codebase.

@germanne
Copy link

germanne commented May 6, 2025

I would be also very interested in this feature. Also the goal is not to get a revert PR but to quickly put the branch back to its state before merging, which can be very useful in some cases of problems

@lunny
Copy link
Member

lunny commented May 7, 2025

If you mean reverting a commit, that has been implemented for a long time.

Image

@germanne
Copy link

germanne commented May 8, 2025

that's exactly my point, I'd like to be able to do that on the MR and viewout any "revert commit"! So reverting without any trace of the merge

@wxiaoguang
Copy link
Contributor

wxiaoguang commented May 8, 2025

that's exactly my point, I'd like to be able to do that on the MR and viewout any "revert commit"! So reverting without any trace of the merge

That's hard-reset + force-push, which is an unacceptable operation in most development environments, especially when it is done on the "main" branch. I do not think Gitea should provide such support on the UI (it would cause more problems). If you really need to "revert a commit without any trace", you need to do that by your git client and tell all your developers what happens.

@germanne
Copy link

germanne commented May 8, 2025

I thought this was available on Gitlab and indeed just checked and it's not, so ok my bad, sorry for that and thanks for the answer

@wxiaoguang wxiaoguang added the issue/workaround it is or has a workaround label May 8, 2025
@lunny
Copy link
Member

lunny commented May 8, 2025

I think this operation should be try to create a revert pull request. And of course, like @wxiaoguang said, sometimes it will fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented issue/workaround it is or has a workaround type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

No branches or pull requests

5 participants