We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently our repo history, and subsequently the release change logs, are full of a wild array of message styles.
We should create a status check that blocks merge until the PR title meets a certain standard.
Here are some ideas as a starting point...
where x is "features", "threats", "controls", "category", or "family":
x
add(x): <message>
change(x): <message>
remove(x): <message>
and for other changes:
ci: <message>
docs: <message>
The text was updated successfully, but these errors were encountered:
I can snag this one and use one of my reusable workflows. PR inbound.
Sorry, something went wrong.
Adhering to conventional-commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) I suggest the following types and scopes:
feat(ci): Add pr-title workflow
3393463
Closes finos#618 - [x] verify PR title is adhering to designed scopes and types Signed-off-by: jmeridth <[email protected]>
jmeridth
Successfully merging a pull request may close this issue.
Currently our repo history, and subsequently the release change logs, are full of a wild array of message styles.
We should create a status check that blocks merge until the PR title meets a certain standard.
Here are some ideas as a starting point...
where
x
is "features", "threats", "controls", "category", or "family":add(x): <message>
change(x): <message>
remove(x): <message>
and for other changes:
ci: <message>
docs: <message>
The text was updated successfully, but these errors were encountered: