Codeberg/Community
54
325
Fork
You've already forked Community
12

AGit PR not updating after force push by maintainer #1768

Closed
opened 2025年01月20日 15:11:19 +01:00 by embr · 2 comments

Comment

Hi,
This PR: gorgon/gorgon#31

Was opened on a project of mine, by my roommate, who just asked me IRL to rebase it on main for her. So I checked it out, rebased it, did a git push --force to update it, and... now it's in a bit of an odd state.

The "Commits" and "Files Changed" tabs are both updated, but the "Conversation" tab has not. Webhooks also didn't fire, so my CI isn't building the PR. I kinda need this merged, so I'm gonna do so manually in an hour, but this is a very interesting behaviour that might be worth investigating further.

### Comment Hi, This PR: https://codeberg.org/gorgon/gorgon/pulls/31 Was opened on a project of mine, by my roommate, who just asked me IRL to rebase it on main for her. So I checked it out, rebased it, did a `git push --force` to update it, and... now it's in a bit of an odd state. The "Commits" and "Files Changed" tabs are both updated, but the "Conversation" tab has not. Webhooks also didn't fire, so my CI isn't building the PR. I kinda need this merged, so I'm gonna do so manually in an hour, but this is a very interesting behaviour that might be worth investigating further.
Owner
Copy link

Could you elaborate on what you did exactly? git push --force is not the desired way to update AGit PRs. See https://forgejo.org/docs/next/user/agit-support/#parameters

Could you elaborate on what you did exactly? `git push --force` is not the desired way to update AGit PRs. See https://forgejo.org/docs/next/user/agit-support/#parameters

I'm considering that the matter has been resolved, given that there has been no further response - and that there are reasonable grounds to believe that what Otto said is enough of an explanation.

feel free to reopen / ping me if that is not the case

I'm considering that the matter has been resolved, given that there has been no further response - and that there are reasonable grounds to believe that what Otto said is enough of an explanation. feel free to reopen / ping me if that is not the case
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1768
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?