Starter
Try AI PR review.
- 2 reviewers
- Code Review
- Security Review
- 3 seats included
- 15,000 credits to start, then 5,000/mo
- About 70 reviews to start, then about 25 a month
- Unlimited repos
A message can be a valid Conventional Commit and still fail commitlint. The specification accepts any type in any case, so Feat: add dark mode is fine by it.[1] commitlint's conventional config accepts eleven types, all in lower case, so it fails that line on two rules.[2]
What lands on your pull request · Code Review
billing/checkout.ts:42 · A timed-out response can charge the order twice- await payments.charge(order);+ await payments.charge(order, {+ idempotencyKey: order.id,+ });
Paste the subjects from your branch, or one whole message. You get both verdicts for each line, the reason a line fails, and the release the commits call for. It is free and needs no signup, and nothing you paste leaves your browser.
It runs in your browser. Nothing is sent or stored, and there is no signup.
5 of 8 follow the spec, and 3 of the 7 that commitlint checks pass it. Together they call for a major release.
feat(auth): add passkey sign-inConventional Commitpasses commitlinta minor release
fix: Handle an empty diff.Conventional Commitfails commitlint (subject-case, subject-full-stop)a patch release
subject-case: subject must not start with a capital lettersubject-full-stop: subject may not end with a full stopdocs: update the setup guideConventional Commitpasses commitlintno release
Feat: add dark modeConventional Commitfails commitlint (type-enum, type-case)a minor release
type-enum: type must be one of build, chore, ci, docs, feat, fix, perf, refactor, revert, style, testtype-case: type must be lower casechore(deps)!: drop Node 18Conventional Commitpasses commitlintbreaking, a major release
refactor : split the review queueNot a Conventional Commitfails commitlint (type-empty, subject-empty)
type-empty: type may not be emptysubject-empty: subject may not be emptyMerge pull request #12 from acme/passkeysNot a Conventional Commitcommitlint skips it by default
update readmeNot a Conventional Commitfails commitlint (type-empty, subject-empty)
type-empty: type may not be emptysubject-empty: subject may not be emptyThe spec requires feat for a new feature and fix for a bug fix, and it allows any other type.[1] commitlint allows only build, chore, ci, docs, feat, fix, perf, refactor, revert, style and test, written in lower case.[2]
The spec says nothing about either. commitlint fails a description that starts with a capital letter, though it ignores words in quotes or backticks, and it fails a header that ends with a full stop.[2]
The spec sets no limit. commitlint fails a header longer than 100 characters, and any body or footer line longer than 100 unless that line holds a URL.[2]
commitlint skips headers such as Merge pull request #12, Revert "…" and fixup! without checking them.[3] None of them is a Conventional Commit. If you squash merge with the pull request title as the message, that title is the commit your main branch keeps, so check it too.
Put ! right before the colon, as in feat(api)!:, or add a footer that starts BREAKING CHANGE: or BREAKING-CHANGE:. The spec requires the capitals, and it names only those two tokens. A footer written breaking change: or BREAKING_CHANGE: does not mark a breaking change.[1]
// commitlint.config.js
export default { extends: ["@commitlint/config-conventional"] };The spec ties three things to a version. A breaking change calls for a major release, feat for a minor one and fix for a patch.[1] semantic-release's default rules also release perf and revert commits as a patch.[4]
Run git log --format=%s main..HEAD to print the subjects on your branch. Paste them above, one per line, and add the pull request title if you plan to squash with it.
A good subject says what a change claims to do. IonWarp reads the pull request's diff to check it, and posts one comment with the file and line each finding points to.
One workspace price with seats included. Credits pool across your team. Unlimited repos on every plan.
Try AI PR review.
Get AI PR review right from day 1.
Scale AI PR review.
Custom reviewers + credits · GitHub Enterprise · SSO/SAML + audit logs · Custom security review + SLA
It is a format for commit messages. The first line holds a type such as feat or fix, an optional scope in parentheses, an optional ! for a breaking change, a colon and a space, and then a description. A body and footers may follow, each after a blank line.
Not under the spec. It says tools must not treat them as case sensitive, except for BREAKING CHANGE, which must be in capitals. commitlint's conventional config does require lower-case types.
@commitlint/config-conventional allows eleven types, build, chore, ci, docs, feat, fix, perf, refactor, revert, style and test. You can change the list in your own config.
Put ! right before the colon, as in feat(api)!: drop the v1 endpoint, or add a footer that starts BREAKING CHANGE: and describes the change. Either one calls for a major release.
Yes. There is no signup and nothing to install. It runs in your browser, and nothing you paste is sent anywhere.