nbrempel

Hey! Mostly just rebase out of habit actually, but I've been exploring --update-refs recently.

Two things come to mind that I don't love about `gt`:

- the philosophy of "every commit is a PR" falls apart sometimes. Sometimes I want to logically separate commits in a PR—but not every commit passes CI. This makes it easier to review. Or call out optional changes that can easily be dropped.

- It broke my workflow in a few ways. The one thing I notice the most is that I like to "pop" a commit into staged changes and make edits. So I can easily see a diff of what I'm editing. I expected `gt modify` to do this. So instead I git reset --soft, commit, and `gt submit`

Thanks for the comment :)

I use Graphite at {{ day job }} and it's pretty good. I strongly dislike having to use their git wrapper CLI `gt` though. git does already support this out of the box.

So instead, this uses git primitives and just drops that handy comment in Github to visualize the stack.

Yeah, I'd like to offer paid features such as custom domains, private domains, etc. For now, the cost is pretty low to serve text out of GCS.

It would be nice if we could see the last 10 years.

Thanks for reading everyone. I’ve gotten some feedback over on Reddit as well that the example is not effectively showing the benefits of SIMD. I plan on revising this.

One of my goals of writing these articles is to learn so feedback is more than welcome!

We've started using this. It's fantastic! Great work. Thank you :)