[Feature request] Reverting a pull request #3073

New Issue

GiteaMirror · 2025-11-02T04:59:49-06:00

GiteaMirror commented

2025-11-02 04:59:49 -06:00

Originally created by @ghost on GitHub (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

Originally created by @ghost on GitHub (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

GiteaMirror added the type/feature issue/confirmed issue/workaround labels 2025-11-02 04:59:49 -06:00

GiteaMirror commented

2025-11-02 04:59:50 -06:00

@stale[bot] commented on GitHub (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[bot] commented on GitHub (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.

GiteaMirror commented

2025-11-02 04:59:51 -06:00

@6543 commented on GitHub (Oct 9, 2019):

can we add this to v1.11.x ?

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

@6543 commented on GitHub (Oct 9, 2019): can we add this to v1.11.x ? because it sounds very usefull and we dont loose track of it

GiteaMirror commented

2025-11-02 04:59:51 -06:00

@lunny commented on GitHub (Nov 2, 2019):

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

@lunny commented on GitHub (Nov 2, 2019): @6543 but nobody are working on this even I think it's not difficult to implement.

GiteaMirror commented

2025-11-02 04:59:51 -06:00

@su-tiko commented on GitHub (Aug 31, 2020):

Is there any plan to implement this feature? Thanks.

@su-tiko commented on GitHub (Aug 31, 2020): Is there any plan to implement this feature? Thanks.

GiteaMirror commented

2025-11-02 04:59:51 -06:00

@6543 commented on GitHub (Aug 31, 2020):

@vjgarcera plan: well issue is till open ;)

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

@6543 commented on GitHub (Aug 31, 2020): @vjgarcera plan: well issue is till open ;) But no dev has picked it jet, feel free to have a look

GiteaMirror commented

2025-11-02 04:59:52 -06:00

@wxiaoguang commented on GitHub (Dec 15, 2024):

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

@wxiaoguang commented on GitHub (Dec 15, 2024): A commit could be reverted on the web UI, so reverting the PR's commit could revert that PR: ![image](https://github.com/user-attachments/assets/2e5c8397-9f86-4490-a70c-599cb8e6b9e4)

GiteaMirror commented

2025-11-02 04:59:52 -06:00

@lunny commented on GitHub (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.

@lunny commented on GitHub (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.

GiteaMirror commented

2025-11-02 04:59:52 -06:00

@germanne commented on GitHub (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

@germanne commented on GitHub (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

GiteaMirror commented

2025-11-02 04:59:52 -06:00

@lunny commented on GitHub (May 7, 2025):

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

@lunny commented on GitHub (May 7, 2025): If you mean reverting a commit, that has been implemented for a long time. ![Image](https://github.com/user-attachments/assets/d6a9e63f-5ac1-4c05-8636-5c6e345c4080)

GiteaMirror commented

2025-11-02 04:59:52 -06:00

@germanne commented on GitHub (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

@germanne commented on GitHub (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

GiteaMirror commented

2025-11-02 04:59:53 -06:00

@wxiaoguang commented on GitHub (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.

@wxiaoguang commented on GitHub (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.

GiteaMirror commented

2025-11-02 04:59:54 -06:00

@germanne commented on GitHub (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

@germanne commented on GitHub (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

GiteaMirror commented

2025-11-02 04:59:54 -06:00

@lunny commented on GitHub (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.

@lunny commented on GitHub (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.

GiteaMirror referenced this issue

2025-11-02 12:18:10 -06:00

[PR #3073] [MERGED] Fix bugs in issue dashboard stats #16748

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#3073