Does not support viewing the content of force push #6554

New Issue

GiteaMirror · 2025-11-02T06:59:11-06:00

GiteaMirror commented

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

Originally created by @ffbh123456 on GitHub (Dec 20, 2020).

Please see the picture below, github can view the updated content by clicking force-push, but gitea does not support

Originally created by @ffbh123456 on GitHub (Dec 20, 2020). Please see the picture below, github can view the updated content by clicking force-push, but gitea does not support ![image](https://user-images.githubusercontent.com/20750357/102708695-553af700-42df-11eb-92af-9ea612b63bb3.png)

GiteaMirror added the type/proposal label 2025-11-02 06:59:11 -06:00

GiteaMirror closed this issue

2025-11-02 06:59:12 -06:00

GiteaMirror commented

2025-11-02 06:59:12 -06:00

@s-weigand commented on GitHub (Feb 8, 2022):

Just had the same issue, I added a commit to my feature branch with an already opened PR and since it got out of sync I rebased it and force pushed. When I wanted to tell the reviewer which commit addressed the requested changes I couldn't find it in the list of commits shown on the PR page.

@s-weigand commented on GitHub (Feb 8, 2022): Just had the same issue, I added a commit to my feature branch with an already opened PR and since it got out of sync I rebased it and force pushed. When I wanted to tell the reviewer which commit addressed the requested changes I couldn't find it in the list of commits shown on the PR page.

GiteaMirror commented

2025-11-02 06:59:12 -06:00

@M1CK431 commented on GitHub (Apr 4, 2022):

Same here and this is excessively annoying because rewrite history / force push is a very common practice on feature branch when some want to have a clear commit history (very useful in case of revert for example).

@M1CK431 commented on GitHub (Apr 4, 2022): Same here and this is excessively annoying because rewrite history / force push is a very common practice on feature branch when some want to have a clear commit history (very useful in case of revert for example).

GiteaMirror commented

2025-11-02 06:59:12 -06:00

@smartEBL commented on GitHub (Aug 25, 2023):

I think this one was implemented in https://github.com/go-gitea/gitea/pull/22857
Now (starting with 1.20.0) you can view the diff of a force push like so:

I guess this ticket can be closed then.

@smartEBL commented on GitHub (Aug 25, 2023): I think this one was implemented in https://github.com/go-gitea/gitea/pull/22857 Now (starting with 1.20.0) you can view the diff of a force push like so: ![image](https://github.com/go-gitea/gitea/assets/79155718/8ca64125-45f2-40f7-89c7-d3b2c0a42589) I guess this ticket can be closed then.

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#6554