-
Notifications
You must be signed in to change notification settings - Fork 0
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
Recreate commitlint
command in yargs
#75
Comments
GeorgeCadwallader
added a commit
that referenced
this issue
Oct 1, 2024
This will be used to lint the incoming commit messages. Ref: #75
GeorgeCadwallader
added a commit
that referenced
this issue
Oct 1, 2024
These two commands will be used to retrieve commits from the source control provider. One retrieves the latest, current commit; and the other returns a list of commits. The commit list can accept from and to arguments that filter the list of commits that will be returned. Ref: #75
GeorgeCadwallader
added a commit
that referenced
this issue
Oct 1, 2024
Command to lint commits using Commitlint. The command returns an output of information about each commit if there are errors or warnings to report about it. Available arguments are the level of severity to lint, and the commit hash or reference to start linting from. Ref: #75
GeorgeCadwallader
added a commit
that referenced
this issue
Oct 1, 2024
Testing the commitlint command to make sure it's working as expected. Tests include, validating correct and incorrect commit messages and log output assertion. Ref: #75
GeorgeCadwallader
added a commit
that referenced
this issue
Oct 17, 2024
These two commands will be used to retrieve commits from the source control provider. One retrieves the latest, current commit; and the other returns a list of commits. The commit list can accept from and to arguments that filter the list of commits that will be returned. Ref: #75
GeorgeCadwallader
added a commit
that referenced
this issue
Oct 17, 2024
Command to lint commits using Commitlint. The command returns an output of information about each commit if there are errors or warnings to report about it. Available arguments are the level of severity to lint, and the commit hash or reference to start linting from. Ref: #75
GeorgeCadwallader
added a commit
that referenced
this issue
Oct 17, 2024
Testing the commitlint command to make sure it's working as expected. Tests include, validating correct and incorrect commit messages and log output assertion. Ref: #75
AdeAttwood
pushed a commit
that referenced
this issue
Oct 18, 2024
This will be used to lint the incoming commit messages. Ref: #75
AdeAttwood
pushed a commit
that referenced
this issue
Oct 18, 2024
These two commands will be used to retrieve commits from the source control provider. One retrieves the latest, current commit; and the other returns a list of commits. The commit list can accept from and to arguments that filter the list of commits that will be returned. Ref: #75
AdeAttwood
pushed a commit
that referenced
this issue
Oct 18, 2024
Command to lint commits using Commitlint. The command returns an output of information about each commit if there are errors or warnings to report about it. Available arguments are the level of severity to lint, and the commit hash or reference to start linting from. Ref: #75
AdeAttwood
pushed a commit
that referenced
this issue
Oct 18, 2024
Testing the commitlint command to make sure it's working as expected. Tests include, validating correct and incorrect commit messages and log output assertion. Ref: #75
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem to solve
We need to recreate the
commitlint
command in version 2 of the app.Proposal
This command should work the same as it did in version 1.
Further details
One difference is we might use our own implementation of the commitlint package, however this is a potential future thing. The main focus is to replicate functionality for now.
The text was updated successfully, but these errors were encountered: