-
Notifications
You must be signed in to change notification settings - Fork 0
ci: add commit lint workflow #1
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
Conversation
ef4eeba
to
9deeb77
Compare
9deeb77
to
f823d4b
Compare
f823d4b
to
458a89f
Compare
458a89f
to
f4c956e
Compare
The PR title does not follow the Calimero-Network Commit Message Convention Our PR title should have the following structure.
Common errors to avoid:
The linting rules are defined in: More about the Commit Message Convention |
f4c956e
to
cc7797a
Compare
cc7797a
to
25443de
Compare
The PR title Our PR title should have the following structure.
Common errors to avoid:
The linting rules are defined in: More about the Commit Message Convention |
25443de
to
89a217a
Compare
The PR title Our PR title should have the following structure.
Common errors to avoid:
The linting rules are defined in: More about the Commit Message Convention |
89a217a
to
0409990
Compare
The PR title Our PR title should have the following structure.
Common errors to avoid:
The linting rules are defined in: More about the Commit Message Convention |
92143f9
to
39f7e60
Compare
84c74ad
to
43dfbac
Compare
43dfbac
to
ea904c6
Compare
[product] short description
Description
Please include a short description of the change and which issue is fixed.
Please also include relevant motivation and context. List any dependencies that
are required for this change.
Test plan
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Is it possible to add a test case to our
end-to-end tests with changes from this PR? Add screenshots or videos for
changes in the user-interface.
Documentation update
Mention here what part (if any) of public or internal documentation should be
updated because of this PR. Documentation has to be updated no later than
one day after this PR has been merged.