Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
1 of 3 tasks
InExtremaRes opened this issue Aug 31, 2018 · 2 comments
Closed
1 of 3 tasks

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

InExtremaRes opened this issue Aug 31, 2018 · 2 comments
Labels
issue/stale type/enhancement An improvement of existing functionality

Comments

@InExtremaRes
Copy link

InExtremaRes commented Aug 31, 2018

  • 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

@lafriks lafriks added the type/enhancement An improvement of existing functionality label Aug 31, 2018
@stale
Copy link

stale bot commented Jan 11, 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 stale bot added the issue/stale label Jan 11, 2019
@stale
Copy link

stale bot commented Feb 21, 2019

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed Feb 21, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/stale type/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants