Improve clarity on changelog command "--range" argument in a situation where I have two git commit hashes

[gfargo]

Describe the Issue
The other day, I wanted to generate a changelog for a large collection of commits. Despite having the commit hash for the start and end of the range, I found myself struggling to use the --range flag with the changelog command to generate a changelog.

In the end, I just ended up going a slightly different, less accurate, way via

coco changelog -r HEAD~36:HEAD

To Reproduce
Steps to reproduce the behavior:

1. Run the coco changelog command
2. Pass --range or -r parameters with two git commits
3. What format should I be using when passing commits v.s. referencing HEAD 💭

Expected behavior
Maybe we can include a better description in the help output for this command, with more examples?

Screenshots

Desktop:

• OS: MacOS
• Shell: ZSH
• Version: 0.14.8