Closed leseb closed 4 years ago
I'm not sure we want to implement linting inside the engine itself, but having the ability to craft your own lint with the configuration would be neat.
IIUC, you would need to:
AFAICT:
Point 1. is not possible yet, and would require some adding to the condition language Point 2. is already possible. Point 3. could be an action provided by Mergify with your own status check.
Last point: what's preventing you to running commitlint via a GitHub Action?
I'm not sure we want to implement linting inside the engine itself, but having the ability to craft your own lint with the configuration would be neat.
IIUC, you would need to:
- Check that every commit in a PR matches a certain regex
- Check the PR title matches a certain regex
- Post the result to the PR
AFAICT:
Point 1. is not possible yet, and would require some adding to the condition language Point 2. is already possible. Point 3. could be an action provided by Mergify with your own status check.
Last point: what's preventing you to running commitlint via a GitHub Action?
Actually, I've never thought about this, after some investigation it looks like https://github.com/wagoid/commitlint-github-action exactly does what I need.
Thanks!
Before anyone asks, yes I'm aware of the existence of https://github.com/zeke/semantic-pull-requests, so perhaps I can start by explaining why it does not fully work for me:
Just to be clear it's not a complaint against semantic-pull-requests, these are just facts :-).
With that said, I wish Mergify could rely on https://github.com/conventional-changelog/commitlint to parse each commit of a given PR and output any anomaly as part of the PR check status. To go further, Mergify could attempt to read and pass any commitlint configuration it finds in
.github
(see for reference https://github.com/conventional-changelog/commitlint#config).So it would be nice to a new action that does:
Hopefully, that makes sense! Feel free to disregard if this is too out of scope :) Bisous.