Codeberg/Community
60
387
Fork
You've already forked Community
12

Force-push and new commit on repo did not update pull request #2732

Closed
opened 2026年06月07日 10:53:08 +02:00 by kada49 · 3 comments

Comment

I wanted to update a pr on for ziglang/zig, because it needed a rebase and did that. The pr: ziglang/zig#35470

Problem:
My repository (https://codeberg.org/kada49/zig/src/branch/array_hash_map_deprecation_rename) got updated, but the pr did not pick up the changes. I also added a new commit (empty because I didn't want to add unwanted changes) and still the pr did not update.

If you check the pr, no new actions/ci-runs were triggered, still shows up as conflicting and the code did not change. When clicking on the link, that should link to the repo where the changes come from, it shows the correct changes

### Comment I wanted to update a pr on for ziglang/zig, because it needed a rebase and did that. The pr: https://codeberg.org/ziglang/zig/pulls/35470 Problem: My repository (https://codeberg.org/kada49/zig/src/branch/array_hash_map_deprecation_rename) got updated, but the pr did not pick up the changes. I also added a new commit (empty because I didn't want to add unwanted changes) and still the pr did not update. If you check the pr, no new actions/ci-runs were triggered, still shows up as conflicting and the code did not change. When clicking on the link, that should link to the repo where the changes come from, it shows the correct changes
kada49 changed title from (削除) Force-push on repo did not update pull request (削除ここまで) to Force-push and new commit on repo did not update pull request 2026年06月07日 10:56:12 +02:00
Author
Copy link

Correction: a ci-run is started, but the pr does not show that (https://codeberg.org/ziglang/zig/actions/runs/4322/jobs/0/attempt/1)

Correction: a ci-run is started, but the pr does not show that (https://codeberg.org/ziglang/zig/actions/runs/4322/jobs/0/attempt/1)

Hi, could you push yet another empty commit? We can't re-trigger a event like that from our side. If the pull request is then still not updated we can do some extra investigation.

Hi, could you push yet another empty commit? We can't re-trigger a event like that from our side. If the pull request is then still not updated we can do some extra investigation.
Author
Copy link

this time it fixed the pr, thanks for the time!

this time it fixed the pr, thanks for the time!
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 Forgejo)
upstream
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Forgejo, Weblate, 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
2 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#2732
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?