Michael Caterisano

Thanks @andyfeller for the quick reply! Your repro steps are not quite right. Here's a[ public repo](https://github.com/michaelcaterisano/gh-release-bug) where I've reproduced the issue. The steps I took were: 1. create a...

And here are the debug logs ``` gh-release-bug git:(feature-branch) ✗ GH_DEBUG=api gh release create 2025-04-22T131120Z --draft --fail-on-no-commits --notes-start-tag 2025-04-22T130509Z --generate-notes [git remote -v] [git config --get-regexp ^remote\..*\.gh-resolved$] * Request at...

It looks like the log shows that the comparison made by `--fail-on-no-commits` is between the most recent release and `HEAD` of my default branch (main), rather than between the most...

@andyfeller friendly bump

@andyfeller @williammartin Thanks for your reply! The use case I was hoping to support was a remote tag on a branch other than the default (i.e. a remote feature branch)....

Thanks @bryanjos! We've already discussed, but I'll add my thoughts here as well. I encountered unexpected behavior with `config/2` when I returned `{:error, map}`, assuming its api would be the...

I don't think this is just a naming issue, the docs seem to be wrong here: ``` graphql_ws Used by the graphql-ws library This subprotocol is the default value and...