-
Notifications
You must be signed in to change notification settings - Fork 312
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
CI: Enforce conventional commits and signed commits #1119
Comments
Assign this to me, I have experience with GHA from my fiat dev career. |
Personally I'd love to see this, I remember agreeing with @evanlinjin that it would be useful to enforce signed commits in CI; while I don't remember who but someone wasn't fond of enforcing conventional commits (maybe @notmandatory?) |
Yes, I plan to add the conventional commits commented out in the new EDIT: Or we just don't make that CI check mandatory for a PR to be merged |
I like this! Just assigned it to you, happy hacking |
Closes bitcoindevkit#1119. Creates `commits.yml` in `.github/workflows/` directory with a new GH Action that has 2 jobs: 1. `signed-commits`: uses [`1Password/check-signed-commits-action`](https://github.com/1Password/check-signed-commits-action) to check if all commits in the PR are signed. 1. `conventional-commits`: uses [`webiny/action-conventional-commits`](https://github.com/webiny/action-conventional-commits) to check if all commits in the PR follows the conventional commits](https://www.conventionalcommits.org/en/v1.0.0-beta.2/), i.e. they are prefixed with `fix`, `refactor`, `feat` etc.
Concept ACK. We already have "Require signed commits" enabled for merging PRs to the bdk |
Closes bitcoindevkit#1119. Creates `commits.yml` in `.github/workflows/` directory with a new GH Action that has 2 jobs: 1. `signed-commits`: uses [`1Password/check-signed-commits-action`](https://github.com/1Password/check-signed-commits-action) to check if all commits in the PR are signed. 1. `conventional-commits`: uses [`aevea/commitsar`](https://github.com/aevea/commitsar) to check if all commits in the PR follows the conventional commits](https://www.conventionalcommits.org/en/v1.0.0-beta.2/), i.e. they are prefixed with `fix`, `refactor`, `feat` etc.
Closes bitcoindevkit#1119. Creates `commits.yml` in `.github/workflows/` directory with a new GH Action that has 2 jobs: 1. `signed-commits`: uses [`1Password/check-signed-commits-action`](https://github.com/1Password/check-signed-commits-action) to check if all commits in the PR are signed. 1. `conventional-commits`: uses [`aevea/commitsar`](https://github.com/aevea/commitsar) to check if all commits in the PR follows the conventional commits](https://www.conventionalcommits.org/en/v1.0.0-beta.2/), i.e. they are prefixed with `fix`, `refactor`, `feat` etc.
Closes bitcoindevkit#1119. Creates `commits.yml` in `.github/workflows/` directory with a new GH Action that has 2 jobs: 1. `signed-commits`: uses [`1Password/check-signed-commits-action`](https://github.com/1Password/check-signed-commits-action) to check if all commits in the PR are signed. 1. `conventional-commits`: uses [`cocogitto/cocogitto-action`](https://github.com/cocogitto/cocogitto-action) based on [`cocogitto`](https://crates.io/crates/cocogitto) to check if all commits in the PR follows the conventional commits](https://www.conventionalcommits.org/en/v1.0.0-beta.2/), i.e. they are prefixed with `fix`, `refactor`, `feat` etc.
Closes bitcoindevkit#1119. Creates `commits.yml` in `.github/workflows/` directory with a new GH Action that has 2 jobs: 1. `signed-commits`: uses [`1Password/check-signed-commits-action`](https://github.com/1Password/check-signed-commits-action) to check if all commits in the PR are signed. 1. `conventional-commits`: uses [`cocogitto/cocogitto-action`](https://github.com/cocogitto/cocogitto-action) based on [`cocogitto`](https://crates.io/crates/cocogitto) to check if all commits in the PR follows the conventional commits](https://www.conventionalcommits.org/en/v1.0.0-beta.2/), i.e. they are prefixed with `fix`, `refactor`, `feat` etc.
Closes bitcoindevkit#1119. Creates `commits.yml` in `.github/workflows/` directory with a new GH Action that has 2 jobs: 1. `signed-commits`: uses [`1Password/check-signed-commits-action`](https://github.com/1Password/check-signed-commits-action) to check if all commits in the PR are signed. 1. `conventional-commits`: uses [`cocogitto/cocogitto-action`](https://github.com/cocogitto/cocogitto-action) based on [`cocogitto`](https://crates.io/crates/cocogitto) to check if all commits in the PR follows the conventional commits](https://www.conventionalcommits.org/en/v1.0.0-beta.2/), i.e. they are prefixed with `fix`, `refactor`, `feat` etc.
During the devcall today @danielabrozzoni mentioned that the enforcement of both conventional commits (the
fix
,refactor
, `feat, etc.) and the signed commits are manual.We should add a CI step to automate this.
For the conventional commits, we have
webiny/action-conventional-commits
.And for the signed commits, we have
1Password/check-signed-commits-action
.The text was updated successfully, but these errors were encountered: