Skip to content

Conversation

metaclips
Copy link
Owner

[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.

@metaclips metaclips force-pushed the metaclips/add_commit_lint branch 4 times, most recently from ef4eeba to 9deeb77 Compare July 7, 2025 20:37
@metaclips metaclips changed the title ci: add commit lint workflow bad PR title Jul 7, 2025
@metaclips metaclips force-pushed the metaclips/add_commit_lint branch from 9deeb77 to f823d4b Compare July 7, 2025 20:40
@metaclips metaclips changed the title bad PR title bad PR title 1 Jul 7, 2025
@metaclips metaclips force-pushed the metaclips/add_commit_lint branch from f823d4b to 458a89f Compare July 7, 2025 20:44
@metaclips metaclips changed the title bad PR title 1 bad PR title Jul 7, 2025
@metaclips metaclips force-pushed the metaclips/add_commit_lint branch from 458a89f to f4c956e Compare July 7, 2025 20:51
@metaclips metaclips changed the title bad PR title bad PR title 66 Jul 7, 2025
Copy link

github-actions bot commented Jul 7, 2025

The PR title does not follow the Calimero-Network Commit Message Convention
https://github.com/calimero-network/core/blob/master/CONTRIBUTING.md#commit-message-style

Our PR title should have the following structure.

<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>

Common errors to avoid:

  1. The commit header (): must be in lower case.
  2. Allowed type values are: build, ci, docs, feat, fix, perf, refactor, test.

The linting rules are defined in:
https://github.com/calimero-network/core/blob/master/commitlint.config.js

More about the Commit Message Convention
https://github.com/calimero-network/core/blob/master/CONTRIBUTING.md#commit-message-style

@metaclips metaclips force-pushed the metaclips/add_commit_lint branch from f4c956e to cc7797a Compare July 7, 2025 20:53
Repository owner deleted a comment from github-actions bot Jul 7, 2025
@metaclips metaclips force-pushed the metaclips/add_commit_lint branch from cc7797a to 25443de Compare July 7, 2025 21:20
Copy link

github-actions bot commented Jul 7, 2025

The PR title bad PR title 66 does not follow the Calimero-Network Commit Message Convention
https://github.com/calimero-network/core/blob/master/CONTRIBUTING.md#commit-message-style

Our PR title should have the following structure.

<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>

Common errors to avoid:

  1. The commit header (): must be in lower case.
  2. Allowed type values are: build, ci, docs, feat, fix, perf, refactor, test.

The linting rules are defined in:
https://github.com/calimero-network/core/blob/master/commitlint.config.js

More about the Commit Message Convention
https://github.com/calimero-network/core/blob/master/CONTRIBUTING.md#commit-message-style

@metaclips metaclips force-pushed the metaclips/add_commit_lint branch from 25443de to 89a217a Compare July 7, 2025 21:20
Copy link

github-actions bot commented Jul 7, 2025

The PR title bad PR title 66 does not follow the Calimero-Network Commit Message Convention
https://github.com/calimero-network/core/blob/master/CONTRIBUTING.md#commit-message-style

Our PR title should have the following structure.

<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>

Common errors to avoid:

  1. The commit header (): must be in lower case.
  2. Allowed type values are: build, ci, docs, feat, fix, perf, refactor, test.

The linting rules are defined in:
https://github.com/calimero-network/core/blob/master/commitlint.config.js

More about the Commit Message Convention
https://github.com/calimero-network/core/blob/master/CONTRIBUTING.md#commit-message-style

@metaclips metaclips changed the title bad PR title 66 ci: add commit lint workflow Jul 7, 2025
@metaclips metaclips changed the title ci: add commit lint workflow ci: add commit lint workflow aa Jul 7, 2025
@metaclips metaclips changed the title ci: add commit lint workflow aa ci: add commit lint workflow Jul 7, 2025
@metaclips metaclips force-pushed the metaclips/add_commit_lint branch from 89a217a to 0409990 Compare July 8, 2025 10:07
@metaclips metaclips changed the title ci: add commit lint workflow cj: add commit lint workflow Jul 8, 2025
Copy link

github-actions bot commented Jul 8, 2025

The PR title cj: add commit lint workflow does not follow the Calimero-Network Commit Message Convention
https://github.com/calimero-network/core/blob/master/CONTRIBUTING.md#commit-message-style

Our PR title should have the following structure.

<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>

Common errors to avoid:

  1. The commit header (): must be in lower case.
  2. Allowed type values are: build, ci, docs, feat, fix, perf, refactor, test.

The linting rules are defined in:
https://github.com/calimero-network/core/blob/master/commitlint.config.js

More about the Commit Message Convention
https://github.com/calimero-network/core/blob/master/CONTRIBUTING.md#commit-message-style

@metaclips metaclips force-pushed the metaclips/add_commit_lint branch 5 times, most recently from 92143f9 to 39f7e60 Compare July 8, 2025 13:46
@metaclips metaclips force-pushed the metaclips/add_commit_lint branch 2 times, most recently from 84c74ad to 43dfbac Compare July 8, 2025 14:06
@metaclips metaclips changed the title cj: add commit lint workflow ci: add commit lint workflow Jul 8, 2025
@metaclips metaclips force-pushed the metaclips/add_commit_lint branch from 43dfbac to ea904c6 Compare July 8, 2025 14:13
@metaclips metaclips closed this Jul 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant