Interesting. That seems to work if your work is not associated with an issue tracker. Many use issue trackers and like to link each branch or PR/MR to an issue tracker.

We've done the same thing, but we only link JIRA tickets to PRs, so when I open a PR, I stick it in the PR description body.

OK, so it is possible that when the gibr pr command gets added that it could be helpful. My thought is for it to automate the creation of the PR and will contain the description which links to the Jira issue.

I have not gotten there yet though

I was doing that for a while with some CLI scripts, never really melded them together, but I had one from before I started using JJ that would make a new git branch named off a JIRA ticket, and a newer one that wrapped up the various jj and github gh cli invocations to create a PR off a branch.

The jira cli util I used, go-jira, hasn't been updated to use the new Atlassian APIs, and I haven't spent too much time looking for a replacement.

https://github.com/paradox460/dotfiles/blob/main/dot_bin/exe... - This creates PRs based off a few different approaches, the -c flag lets you do nameless branches

https://github.com/paradox460/dotfiles/blob/main/dot_bin/exe... - is the one that would fetch tickets from JIRA and make new branches off of it