conform
conform copied to clipboard
Policy enforcement for your pipelines.
When using conventional commits, allow the use of `fixup! ` or `fixup! ` syntax, which are both recognized by `git rebase --autosquash` later on.
With the top-level `policies` being a list, is it expected that one may introduce multiple variants of the "commit" or "license" policies? This seems like undefined behavior since there's nothing...
I use a commit format like this: `feat: KEY-123: implement a feature` But this fails the Header Case is lower check with `Commit header case is not lower`. I'd prefer...
I enjoy adding a mapped emoji in the log to categorize the conventional commit changes. ``` refactor(something): 🔨 align splines to resolve x ``` conform will fail despite using imperative...
Using `mycila/license-maven-plugin` gives the possibility to maintain one `LICENSE` file in the repository and the plugin is able to apply it onto several file types. In that way, I am...
I would like to specify license header file. It is common to store a license file e.g. `LICENSE.txt` or `LICENSE` within the repository. The license file path option shall be...
We should take inspiration from https://github.com/frapposelli/wwhrd.
Conform should create a comment on a PR with details on failures, and hints on how to resolve the issue.
The first line of a commit message is always read as the header even if it's a comment With a commit template like so: ``` # Some top comment #...