Git commit prefix with upcased result [git.commitPrefix]

[dakotahp]

I discovered the commitPrefix config functionality which is awesome. It helps me be more consistent and saves me time.

My company uses Linear which has a button to copy a suggested branch name off of tickets. That is great, but what is annoying is their branch names have the ticket/project prefix lower cased. So a ticket with a name of APP-123 Add Feature Flag would copy a branch name to my clipboard with firstnamelast/app-123-add-feature-flag. I'd prefer it just copy the APP part verbatim with the same casing, but alas, it doesn't.

What I was hoping to do was find a reasonable way to upcase the matched string because the commit prefix copies as [app-123] which is better than nothing, but ideally would have the real casing. Between the Linear copy branch name and this functionality, I'm saving time. I was hoping if someone thought of a way to upcase the matched text. Since the regex use isn't find and replace, I don't think \U works in it so perhaps it's a more complicated thing that isn't worth it.

[stefanhaller]

Since the regex use isn't find and replace, I don't think \U works in it

I would have expected \U to work, but apparently the go regex package doesn't support it. I'm afraid I don't have a good suggestion how to solve this. Anybody else have an idea how we can make this work?

[dakotahp]

Thanks for the response. I added \U to the replace value, assuming that was used in the matching part. The \U was added verbatim to the commit prefix 😄 . I never did try in the actual regex itself so I probably should, out of curiosity.

One thing that occurred to me is that if I just change the casing in the branch name once, then the commit prefixes for the commits are all fine. Better to just get the annoyance out of the way one time, since I'd be likely to make more than a single commit on most branches. That's a way to get good use out of the functionality and do the manual change once so I enjoy the automated functionality for all the commits on the branch. Rather than changing the casing manually for each commit.