-
Notifications
You must be signed in to change notification settings - Fork 15
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
Save-Branch #4
Comments
|
Convince me @dahlbyk ... |
Maybe I'm too far in the weeds, but to me there is an important distinction between a Commit (content + parent(s) + metadata) and a Branch (a reference that updates when you commit while it's checked out). Would The same would go for The others align well for manipulating the branch references themselves, a la |
I guess if we make "index" a noun, we could reuse it in a few other places. And of course, maybe I'm not far enough in the weeds (If so, can you give me a simple script test-case/example?)
I guess the question is how much are we simplifying this command? I mean, I'm taking it for granted that we're not going to expose most of the built-in parameters. After all, I love a good fixup/squash/reuse with rebase interactive, but:
|
For the
Yep - it's called a "detached HEAD". You might get there if you
Yep. Not super common since creating branches is so cheap, but nothing prevents it and I do so every once in a while. Simple example:
Agree 100% that many parameters won't have any use. Like That said, I expect (hope?) you'll find enough more advanced |
Once you've added some work to the index, you have to commit it.
The text was updated successfully, but these errors were encountered: