Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Turn all changes after latest origin/main into a branch

Parent

Turn all changes after latest origin/main into a branch

+2
−0

I have a git history that basically looks like this:

* commit: XXX (HEAD -> main)
|
|
* commit: YYY
|
|
* commit: ZZZ (origin/main)
|
|
...

Now I would like to turn everything after the last origin/main into a named branch (that is, the changed repository would look as if I branched at commit: ZZZ).

Is this possible, and if so, what is the best way to do it?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+2
−0

I handle this with:

  1. Create a new branch with same commits
  2. Delete commits from main branch

In the situation shown, if you do git checkout -b new_branch it will create a new branch with the same commits. You then switch back to main and get rid of the commits on it with git reset HEAD~2.

You can use ZZZ instead of HEAD~2 as the argument to reset if you don't want to count them. I think origin/main might also work. You can pass --hard so that it doesn't leave uncommitted files for you to clean up.

This is also known as "I forgot to switch to a feature branch before making my commits".

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

2 comment threads

Misunderstands branches (2 comments)
Works for me (1 comment)
Misunderstands branches
user253751‭ wrote 3 months ago

This works, but it makes a hash out of the reasons it works, since commits aren't added or removed to branches, but rather branches are pointers to their latest commits. It might mislead someone trying to understand git better.

TraceReilly‭ wrote about 1 month ago

@Undertale Yellow Git works in such a way that each commit in a repository is assigned a unique SHA-1 (or SHA-256 in some newer systems) hash, which identifies that commit and ensures its integrity.