You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As of now, the cog check command can be run either on all commits, or only on commits starting from the latest tag. There is no option to run cog check on a commit range (say, the commits associated with a PR).
Describe the solution you'd like
It would be preferable if we could have an option to run the cog check command on a commit range as well. I did go through the code, and noticed that the necessary utilities to parse a revision range from a string are already available, so this should be a simple addition. I'd be happy to open a PR if required.
Describe alternatives you've considered
For the exact problem I'm trying to solve (checking commits in a PR for compliance to the conventional commit specification), the cocogitto bot is a solution. However, we also have an additional requirement that the PR title must also comply to the conventional commit specification since we do squash merging. To solve for this, I was hoping to run cog verify against the PR title, and cog check against the commit range in a single workflow. I'm open to any other solutions you may have.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As of now, the
cog check
command can be run either on all commits, or only on commits starting from the latest tag. There is no option to runcog check
on a commit range (say, the commits associated with a PR).Describe the solution you'd like
It would be preferable if we could have an option to run the
cog check
command on a commit range as well. I did go through the code, and noticed that the necessary utilities to parse a revision range from a string are already available, so this should be a simple addition. I'd be happy to open a PR if required.Describe alternatives you've considered
For the exact problem I'm trying to solve (checking commits in a PR for compliance to the conventional commit specification), the cocogitto bot is a solution. However, we also have an additional requirement that the PR title must also comply to the conventional commit specification since we do squash merging. To solve for this, I was hoping to run
cog verify
against the PR title, andcog check
against the commit range in a single workflow. I'm open to any other solutions you may have.Additional context
N/A
The text was updated successfully, but these errors were encountered: