You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8f11eb4
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/changelog.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ page that documents it.
11
11
12
12
| Version | What changed | Documented in |
13
13
|---|---|---|
14
+
|[2.23.0](#v2230)|`commit-check-ci` checks a whole merge or pull request in one GitLab CI job or Bitbucket Pipelines step |[GitLab CI, Bitbucket and Azure Pipelines](guides/other-ci.md)|
14
15
|[2.22.0](#v2220)|`--pr-title` checks a pull or merge request title on any CI; the rebase check works in Bitbucket pull request steps and GitLab merged results pipelines |[GitLab CI, Bitbucket and Azure Pipelines](guides/other-ci.md#merge-request-title-and-description) · [CC202](rules.md#cc202)|
15
16
|[2.21.1](#v2211)| Subject length rules leave out a squash merge's ` (#123)` and skip Dependabot and Renovate commits |[CC004](rules.md#cc004) · [CC005](rules.md#cc005)|
16
17
|[2.21.0](#v2210)| A pull request description must tick one of its template's AI declaration checkboxes (opt-in) |[CC501](rules.md#cc501) · [Requiring the template's AI declaration](guides/policies.md#requiring-the-templates-ai-declaration)|
@@ -43,6 +44,16 @@ page that documents it.
43
44
|[2.5.0](#v250)| Organization-wide config with `inherit_from`|[Across an organization](guides/organization.md)|
44
45
|[2.0.0](#v200)| Configuration moved from YAML to TOML — breaking |[Migrating from v1](migration.md)|
45
46
47
+
## v2.23.0 (2026-11-19) { #v2230 }
48
+
49
+
### Added
50
+
51
+
*`commit-check-ci` checks the merge or pull request a GitLab CI job or Bitbucket Pipelines step runs for: the source branch and every commit the request adds, and with an option each the title, the description, the commits' authors and their files. ([GitLab CI, Bitbucket and Azure Pipelines](guides/other-ci.md), [#714](https://github.com/commit-check/commit-check/pull/714))
52
+
53
+
### Fixed
54
+
55
+
* A pull request title or description that fails is headed `Rejected by Commit Check`, not `Commit rejected`: neither is a commit. ([Requiring the template's AI declaration](guides/policies.md#requiring-the-templates-ai-declaration), [#713](https://github.com/commit-check/commit-check/pull/713))
Copy file name to clipboardExpand all lines: docs/guides/integrations.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,8 @@ developer sees locally and what is enforced on the pull request.
9
9
|[Pre-commit hook](pre-commit.md)| As the message is written | Yes — `--no-verify`|`.pre-commit-config.yaml` in each repository |
10
10
|[GitHub Action](github-actions.md)| On every push and pull request, in CI | No | A workflow file in each repository |
11
11
|[GitHub App](github-app.md)| On every push and pull request, hosted | No | Install once for the organization |
12
-
|[GitLab CI, Bitbucket, Azure Pipelines](other-ci.md)| On every merge or pull request, in CI | No | A job in each repository's pipeline file |
12
+
|[GitLab CI, Bitbucket Pipelines](other-ci.md)| On every merge or pull request, in CI | No | Two lines in each repository's pipeline file |
13
+
|[Azure Pipelines, any other CI](other-ci.md#azure-pipelines)| On every pull request, in CI | No | A job in each repository's pipeline file |
13
14
|[Command line](../example.md)| Wherever you call it: a range of commits, a CI you write yourself | — |`pip install commit-check`|
14
15
|[MCP server](mcp.md)| Before the commit exists, inside an AI coding agent | — | One entry in the agent's MCP config |
15
16
|[Python API](python-api.md)| Wherever your own code runs: a bot, a server-side hook, an agent you build | — |`pip install commit-check`, then `import commit_check.api`|
@@ -22,7 +23,8 @@ developer sees locally and what is enforced on the pull request.
22
23
not after a CI round trip.
23
24
-**A policy needs a check that cannot be skipped.** Anyone can pass
24
25
`--no-verify` to a hook. The Action and the App run where that is not
25
-
possible, and a required check keeps a violating change from merging.
26
+
possible, and a required check keeps a violating change from merging. On
27
+
GitLab and Bitbucket the pipeline job is that check.
26
28
-**More than a handful of repositories wants one config.**`inherit_from`
27
29
lets every repository share a base policy and override only what it
28
30
genuinely needs, whichever of the above runs the checks.
@@ -65,6 +67,12 @@ ones created later, gets a **Commit Check** result on each commit of every
65
67
push and pull request, with no workflow file and no CI minutes.
66
68
[Set it up →](github-app.md)
67
69
70
+
## GitLab CI and Bitbucket Pipelines { #gitlab-ci-and-bitbucket-pipelines }
71
+
72
+
One job in the pipeline runs `commit-check-ci`, which finds the merge or pull
73
+
request and checks its branch, every commit it adds and, if asked, its title
74
+
and description. [Set it up →](other-ci.md)
75
+
68
76
## MCP server
69
77
70
78
The same rules as tools for an AI coding agent, so the message is right before
- `--pr-title`checks the title with the message rules a one-line title can
126
125
meet: everything `--message` runs except a body (CC011), a sign-off (CC012)
127
126
and an AI author (CC017). With squash merges the title is often the commit
128
-
message that lands.
129
-
- `--ai-attribution-only`checks the description against your
127
+
message that lands. A draft marker (`Draft:`, `[Draft]`, `(Draft)`) is not
128
+
part of the title that is checked.
129
+
- `--pr-body-ai-attribution`checks the description against your
130
130
`ai_attribution`policy, and, when `[pull_request] ai_declaration_checkboxes`
131
131
is set, that it ticks exactly one AI declaration box (CC501). GitLab task
132
132
lists (`- [x]`, `* [x]`, `1. [x]`) are read like GitHub's.
133
-
- GitLab cuts `CI_MERGE_REQUEST_DESCRIPTION` to its first 2700 characters
134
-
(`CI_MERGE_REQUEST_DESCRIPTION_IS_TRUNCATED` is then `true`), so only that
135
-
part is checked. Put the AI declaration boxes near the top of the merge
136
-
request template, so a long description does not cut them off. To fail a
137
-
description that was cut rather than check part of it, add before the
138
-
description check:
133
+
- GitLab passes a job only the first 2700 characters of a description, so
134
+
only that part is checked, and the job says so when it happens. Put the AI
135
+
declaration boxes near the top of the merge request template, so a long
136
+
description does not cut them off. To fail a description that was cut
137
+
rather than check part of it, add before the `commit-check-ci` line:
139
138
140
139
```yaml
141
140
- test "$CI_MERGE_REQUEST_DESCRIPTION_IS_TRUNCATED" != "true" || { echo "The description is over 2700 characters; GitLab passed only part of it"; exit 1; }
0 commit comments