这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@JohnVillalovos
Copy link
Contributor

Move to using: https://commitizen-tools.github.io/commitizen/

This will enable us to automate our Changelogs when we do releases.

Use tox to setup and run commitizen: https://tox.wiki/

A follow on commit will set this up to run in a GitHub action workflow.

Move to using: https://commitizen-tools.github.io/commitizen/

This will enable us to automate our Changelogs when we do releases.

Use tox to setup and run commitizen: https://tox.wiki/

A follow on commit will set this up to run in a GitHub action
workflow.
 * Enable the commitizen check
 * Update CONTRIBUTING.md with info on conventional commits format
@JohnVillalovos JohnVillalovos merged commit 745d06a into develop Jun 4, 2025
7 checks passed
@JohnVillalovos JohnVillalovos deleted the jlvillal/commitizen branch June 28, 2025 23:18
JohnVillalovos added a commit that referenced this pull request Jun 29, 2025
Was previously using the wrong SHA value in the `cz` or commitizen
check. This was due to the fact that when commits get merged by GitHub
they modify the commit on merge and thus change the SHA :(

This worked for awhile but eventually GitHub pruned the orphan commit
and then the CI started breaking.

This happened in #583
JohnVillalovos added a commit that referenced this pull request Jun 29, 2025
Was previously using the wrong SHA value in the `cz` or commitizen
check. This was due to the fact that when commits get merged by GitHub
they modify the commit on merge and thus change the SHA :(

This worked for awhile but eventually GitHub pruned the orphan commit
and then the CI started breaking.

This happened in #583
JohnVillalovos added a commit that referenced this pull request Jun 29, 2025
Was previously using the wrong SHA value in the `cz` or commitizen
check. This was due to the fact that when commits get merged by GitHub
they modify the commit on merge and thus change the SHA :(

This worked for awhile but eventually GitHub pruned the orphan commit
and then the CI started breaking.

This happened in #583
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.

2 participants