discuss: set default value of `--from-hash` to first commit

[JustBipin]

We've not yet implemented the hash-range feature, but I'm still leaving it here.

context:

upstream project, commitlint has its --to-hash flag optional with its default value set to HEAD. However, the --to-hash is a must.

Proposal:

In cocox, make --from-hash flag optional, and if it's not provided, cocox will lint commits all the way from the first commit

example:

 cocox --to-hash HEAD

But, --to-hash is also optional, so there is an option to not provide both --from-hash and --to-hash flags. which leaves us with just the command cocox .
So maybe we could have another flag like: cocox --all or all subcommand that lints all messages in the main branch.

[aj3sh]

I don't think cocox --all is a good option. It doesn't clearly communicate which commits are being validated, and linting all commits from the repository's first commit is not a common use case.

Making --from-hash optional also seems less practical. Users rarely want to lint commit messages starting from the initial commit.

The reason commitlint makes --to-hash optional and defaults it to HEAD is that commit message linting is typically performed on recent commits. For example:

commitlint --from ae73dc

or

cocox --from-hash ae73dc

is a common workflow because users want to lint commits from a specific point up to the latest commit.

In contrast, a command such as:

cocox --to-hash ae73dc

would lint all commits from the beginning of the repository up to ae73dc, which is not something users usually need.

Because of that, I think --from-hash should remain required for range-based linting, while --to-hash can remain optional and default to HEAD.

[JustBipin]

Yeah, that makes sense. It was just a thought, you know something like.. what if?