[locknitpicker]

> Git has had some additions in the last few years that make this work natively – specifically the --update-refs flag[1] or the rebase.updateRefs config. Combined with `git commit --fixup`, rebase.autoStash, and rebase.autoSquash rebasing stacks becomes a breeze (as long as you work off from the tip of your stack). Add in git-absorb[2] and the heavy-lifting is taken care of.

...or you don't bother with all that and simply do:

- gh stack init

- gh stack push

- gh stack submit

[fphilipe]

Sure, that's possible. I can also use the GitHub app and use a Git abstraction where I don't have to understand Git at all.

The point is that I want to use Git, a tool and skill that is portable to other platforms.

[locknitpicker]

> The point is that I want to use Git, a tool and skill that is portable to other platforms.

You want to use git.

Most people around you want to get things done.

[soledades]

lol and github is the primary obstacle to that in today's software engineering

[KptMarchewa]

That's like, most AI obsoleteable skill you could pick.

[philwelch]

Not at all. One of the tricks of using AI is context management and managing the Git history yourself can be a big part of that. If the AI has a stupid idea and implements it, even when you tell it, “that was a stupid idea, don’t do that, change it back”, the history could persist and the stupid idea will poison the context window every time an agent reads the commit history. It’s even worse if you had the stupid idea!

Also, my current workflow actually has hooks to block agents from creating or changing commits. I know at some point this will be a limit to scaling, but I think that will result in me spending more rather than less time in git.