Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idea: print release notes for a range of versions #6508

Open
mislav opened this issue Oct 25, 2022 · 2 comments
Open

Idea: print release notes for a range of versions #6508

mislav opened this issue Oct 25, 2022 · 2 comments
Labels
enhancement a request to improve CLI gh-release relating to the gh release command

Comments

@mislav
Copy link
Contributor

mislav commented Oct 25, 2022

I often have a need for viewing the entire changelog between two versions. GitHub web UI does not have support for that, but implementing it in GitHub CLI could be trivial.

gh release view <oldversion>..<newversion>
#=> equivalent to `gh release view <version>`, but for every version in the semver range

I'm not a fan of the syntax for ranges I've made up: <oldversion>..<newversion>. Better ideas welcome!

Ranges could also be specified using x or * syntax:

gh release view v3.1.x
#=> prints everything from v3.1.0 to the latest v3.1.x release

For simplicity of output, release assets would not be printed.

@mislav mislav added the enhancement a request to improve CLI label Oct 25, 2022
@shanduur
Copy link
Contributor

I’m going to take that, if still available.

@ijin
Copy link

ijin commented Feb 3, 2023

Sometimes I want to view the entire changelog.

gh release view -a or gh release view --all would be nice to have as well. (I could then pipe it to less)

@williammartin williammartin added the gh-release relating to the gh release command label Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement a request to improve CLI gh-release relating to the gh release command
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants