Skip to content

refs/pull/##/head is not updated after a Rebase and merge #4835

Closed
@InExtremaRes

Description

@InExtremaRes
  • Gitea version (or commit ref): b9ae16d

(using Gitea in Docker with image of Id: "sha256:73bd5621a03339e79b4ef48392aeb68be5eedff40c068763f0d7f73f866a233c")

Description

When a PR is merged using Rebase and merge, commits are rebased but the branch and ref to the PR (refs/pull/#/head) is not updated but left behind in previous commit. I don't know if this will also happen with #4052.

If I update the branch manually (via rebase or reset, and push --force) the branch is updated but the PR and the ref is not. I assume because the PR is closed after merging.

Edit

I was recently trying the same in github (there is no commit graph AFAIK but I pull directly with git fetch remote pull/n/head:local) and the ref is also not updated after the Rebase and merge. So I think this is expected behaviour? In that case, can someone explain me (or point to a doc) why?

Screenshots

Here you can see how the ref and branch is left behind after the Rebase and merge (take attention to the commit with message fix spell)

before merge

image

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions