(Replying to PARENT post)
Yeah, CI solutions can use this command instead of having to write and maintain their own github API interfacing, for example.
👤Cthulhu_🕑5y🔼0🗨️0
(Replying to PARENT post)
I have an open source project that moved from using Jira to track issues and changes to Github. Before, when the project made a release, it would fetch info from Jira to create a changelog.
With this tool, I was able to do something similar using Github as the source of information instead[1].
I fetch the info using the gh tool, output the result into json, and use a python script to format the output which results in a decent looking automatically generated changelog[2].
It's not the most exciting thing, and I could have probably achieved it in a different way using the GraphQL API directly, but for the needs of the project this fit the bill and let me get on with the release.
[1] https://github.com/aurora-scheduler/aurora/blob/master/build...
[2] https://github.com/aurora-scheduler/aurora/blob/master/CHANG...
👤ridv🕑5y🔼0🗨️0
(Replying to PARENT post)
Indeed, a project I work on has a release script which tags a release and all and currently uses a third party tool for the GitHub interactions. Now we can use the first party GitHub CLI commands instead.
👤ocdtrekkie🕑5y🔼0🗨️0
(Replying to PARENT post)