progit2 icon indicating copy to clipboard operation
progit2 copied to clipboard

What new Git features should (or should not) be added to the book?

Open rpjday opened this issue 7 years ago • 6 comments

In addition to tweaking/improving the existing content of the book, is there somewhere a list of newer Git features that are currently not covered at all that should be? A few that leap to mind:

  • worktrees
  • subtrees
  • git replace (supersedes grafts)

and so on. Is the book supposed to be comprehensive, or is it understood that there's just too much to cover in a single book that it's never all going to fit?

rpjday avatar Jun 13 '18 12:06 rpjday

I'd say the goal of the book is to be a great reference and learning guide. We definitely don't want to be encyclopedic, in a lot of cases that level of detail would be useless. (For instance, we don't cover the file format of delta-compressed object stores.)

A couple of motivating examples related to the items on your list:

  • How to take a big repo and split it up (filter-branch with a subtree filter vs. git-subtree split)
  • How to take smaller repos and combine them (subtree merges vs. git-subtree merge)

ben avatar Jun 13 '18 21:06 ben

This issue is a duplicate of #874.

Also @ben, what feature(s) do we want to add?

HonkingGoose avatar Apr 04 '19 11:04 HonkingGoose

I'd review a PR on anything mentioned in this thread, honestly.

ben avatar May 26 '19 18:05 ben

I think worktrees should make it into the book. They are useful for any average user.

jnavila avatar May 27 '19 11:05 jnavila

There is also the new git switch command that was introduced recently.

phil-blain avatar Sep 24 '19 12:09 phil-blain

There's a warning though for git switch, at https://git-scm.com/docs/git-switch#

THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE.

So maybe the ProGit2 project should wait until that command is fully cooked, before writing documentation for the book?

HonkingGoose avatar Sep 25 '19 12:09 HonkingGoose