This message was deleted.

cc @Greg

I’ve been thinking about the same thing @Jonny O'Mahony! How would you want this feature to work with gt?

I'd be much less inclined towards branches - we use Linear and that has the magic branch tracking which I use extensively, but that's just me! But PR titles would be excellent. I think generally a similar pattern to the summary in the description could be really handy for commits, just maybe a little bit scoped down. We're a remote team and something that I've been trying (and somewhat failing) to do is to write really meaningful commit messages so other engineers can gain context on choices made right in their editor instead of having to go and look at the PR description, work through it and identify things. If gt commit had a

-summarise

flag, it'd encourage smaller commits and then leave a meaningful message!

As a fellow Linear user, we also use the linear branch name pretty much exclusively for our branches. A summarize flag would be cool for the body of a commit, but I think I would still want control over the title of the commit.