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

Don't detatch Git HEAD when advance-branches is enabled for a branch #3405

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

emesterhazy
Copy link
Member

When setting the working copy commit, if a single branch points to a parent of the working copy and advance-branches is enabled for that branch, set Git HEAD to the branch instead of detatching at the parent commit.

@emesterhazy emesterhazy force-pushed the advanceable-branches branch from 8a218d2 to f5c4305 Compare March 31, 2024 18:43
@emesterhazy emesterhazy force-pushed the advanceable-branches branch from f5c4305 to bf681cf Compare April 9, 2024 17:54
@emesterhazy emesterhazy force-pushed the advanceable-branches branch 2 times, most recently from 5e10eef to e67d6f7 Compare April 20, 2024 13:29
Base automatically changed from advanceable-branches to main April 20, 2024 14:26
When setting the working copy commit, if a single branch points to a parent of
the working copy and advance-branches is enabled for that branch, set Git HEAD
to the branch instead of detatching at the parent commit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant