From 9eac77662354e27c5474b9717e5c91745431b7eb Mon Sep 17 00:00:00 2001 From: Xianpeng Shen <3353385+shenxianpeng@users.noreply.github.com> Date: Thu, 19 Nov 2026 12:24:24 +0000 Subject: [PATCH 1/2] docs: document commit-check-ci for GitLab CI and Bitbucket, pin v2.23.0 The GitLab CI and Bitbucket Pipelines jobs become two lines: install the package and run commit-check-ci, which v2.23.0 added. Azure Pipelines keeps the hand-written job. Bring the rest of the site in step with v2.23.0: the pre-commit pins, the changelog entry, and the two samples of a failed description check, whose heading that release changed. --- docs/changelog.md | 11 ++ docs/compare/tools.md | 2 +- docs/configuration.md | 2 +- docs/example.md | 2 +- docs/guides/integrations.md | 12 +- docs/guides/other-ci.md | 229 ++++++++++++++++++++---------------- docs/guides/policies.md | 2 +- docs/guides/pre-commit.md | 6 +- docs/rules.md | 2 +- 9 files changed, 154 insertions(+), 114 deletions(-) diff --git a/docs/changelog.md b/docs/changelog.md index c46a54f..4d4dbbf 100644 --- a/docs/changelog.md +++ b/docs/changelog.md @@ -11,6 +11,7 @@ page that documents it. | Version | What changed | Documented in | |---|---|---| +| [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) | | [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) | | [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) | | [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. | [2.5.0](#v250) | Organization-wide config with `inherit_from` | [Across an organization](guides/organization.md) | | [2.0.0](#v200) | Configuration moved from YAML to TOML — breaking | [Migrating from v1](migration.md) | +## v2.23.0 (2026-11-19) { #v2230 } + +### Added + +* `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)) + +### Fixed + +* 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)) + ## v2.22.0 (2026-11-18) { #v2220 } ### Added diff --git a/docs/compare/tools.md b/docs/compare/tools.md index aecf82a..3d7badb 100644 --- a/docs/compare/tools.md +++ b/docs/compare/tools.md @@ -65,7 +65,7 @@ Replace the hook: ```yaml title=".pre-commit-config.yaml" repos: - repo: https://github.com/commit-check/commit-check - rev: v2.22.0 + rev: v2.23.0 hooks: - id: check-message ``` diff --git a/docs/configuration.md b/docs/configuration.md index 07df041..85671cb 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -274,7 +274,7 @@ Used from a hook definition, with no config file anywhere in the repository: ```yaml title=".pre-commit-config.yaml" repos: - repo: https://github.com/commit-check/commit-check - rev: v2.22.0 + rev: v2.23.0 hooks: - id: check-message args: diff --git a/docs/example.md b/docs/example.md index 1478f33..de4dfb2 100644 --- a/docs/example.md +++ b/docs/example.md @@ -186,7 +186,7 @@ pushed: ```yaml title=".pre-commit-config.yaml" repos: - repo: https://github.com/commit-check/commit-check - rev: v2.22.0 + rev: v2.23.0 hooks: - id: check-no-force-push stages: [pre-push] diff --git a/docs/guides/integrations.md b/docs/guides/integrations.md index 3728b6f..8b3046b 100644 --- a/docs/guides/integrations.md +++ b/docs/guides/integrations.md @@ -9,7 +9,8 @@ developer sees locally and what is enforced on the pull request. | [Pre-commit hook](pre-commit.md) | As the message is written | Yes — `--no-verify` | `.pre-commit-config.yaml` in each repository | | [GitHub Action](github-actions.md) | On every push and pull request, in CI | No | A workflow file in each repository | | [GitHub App](github-app.md) | On every push and pull request, hosted | No | Install once for the organization | -| [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 | +| [GitLab CI, Bitbucket Pipelines](other-ci.md) | On every merge or pull request, in CI | No | Two lines in each repository's pipeline file | +| [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 | | [Command line](../example.md) | Wherever you call it: a range of commits, a CI you write yourself | — | `pip install commit-check` | | [MCP server](mcp.md) | Before the commit exists, inside an AI coding agent | — | One entry in the agent's MCP config | | [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. not after a CI round trip. - **A policy needs a check that cannot be skipped.** Anyone can pass `--no-verify` to a hook. The Action and the App run where that is not - possible, and a required check keeps a violating change from merging. + possible, and a required check keeps a violating change from merging. On + GitLab and Bitbucket the pipeline job is that check. - **More than a handful of repositories wants one config.** `inherit_from` lets every repository share a base policy and override only what it 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 push and pull request, with no workflow file and no CI minutes. [Set it up →](github-app.md) +## GitLab CI and Bitbucket Pipelines { #gitlab-ci-and-bitbucket-pipelines } + +One job in the pipeline runs `commit-check-ci`, which finds the merge or pull +request and checks its branch, every commit it adds and, if asked, its title +and description. [Set it up →](other-ci.md) + ## MCP server The same rules as tools for an AI coding agent, so the message is right before diff --git a/docs/guides/other-ci.md b/docs/guides/other-ci.md index c049074..abdb2de 100644 --- a/docs/guides/other-ci.md +++ b/docs/guides/other-ci.md @@ -1,49 +1,15 @@ # GitLab CI, Bitbucket and Azure Pipelines -On GitHub, the [Action](github-actions.md) and the [App](github-app.md) do -this work for you. Everywhere else Commit Check runs as one job in the -pipeline: it is a Python package with no runtime dependencies, so any runner -that can `pip install` can run it, and it reads the same `cchk.toml` as the -hook and the Action. +On GitHub, the [Action](github-actions.md) and the [App](github-app.md) check +every pull request for you. On GitLab CI and Bitbucket Pipelines one command +does that job: `commit-check-ci`, which comes with the package from 2.23.0 +on. It finds the merge or pull request from the variables the CI system sets +and checks the source branch and every commit the request adds, against the +same `cchk.toml` as the hook and the Action. The title, the description, each +commit's author and the files it changes are one option away. -Two things are different from running it on your own machine, and each -example below handles both: - -- **The checkout can be a detached HEAD**, as it is on GitLab and Azure, and - then git has no branch to report. `commit-check --branch` reads the name - from the CI's own variables instead, the merge or pull request's source - branch first, so the jobs call it as is. -- **A merge request has more than one commit.** `--rev` checks one commit, so - the job loops over the commits the merge request adds, as in - [Checking a range of commits](../example.md#checking-a-range-of-commits). - The loop needs the history those commits sit on, so each example turns - shallow cloning off. If the range cannot be read, the job fails rather than - passing with nothing checked. - -Each job runs on merge or pull requests only, because the variables it reads -exist only there. Add `--author-name --author-email` to the `commit-check` -call in the loop to check each commit's author as well, and `--files` to -check the files each commit adds (configured in the `[files]` section). - -The branch check (`--branch`) also covers `require_rebase_target` (CC202), -which needs the target branch in the clone. Neither GitLab nor Bitbucket -fetches it for a merge or pull request, so each job fetches it first. Without -it the rule reports itself as skipped (`rebase target 'main' not found`) and -the job passes. The jobs fetch the request's target branch; if -`require_rebase_target` names a different branch, fetch that one instead. - -!!! note "On 2.18.2 or older" - - Releases before 2.18.3 read only GitHub's variables, so on a detached - checkout `--branch` judges `HEAD`, which is always allowed, and passes - whatever the branch is called. Pipe the name in instead: a value piped - into `--branch` on its own is the name it checks. - - ```console - $ echo "$CI_MERGE_REQUEST_SOURCE_BRANCH_NAME" | commit-check --branch # GitLab - $ echo "$BITBUCKET_BRANCH" | commit-check --branch # Bitbucket - $ echo "${SYSTEM_PULLREQUEST_SOURCEBRANCH#refs/heads/}" | commit-check --branch # Azure - ``` +On Azure Pipelines, and on any other CI, the job is +[written by hand](#azure-pipelines). ## GitLab CI @@ -56,32 +22,67 @@ commit-check: - if: $CI_PIPELINE_SOURCE == "merge_request_event" script: - pip install commit-check - - target="$CI_MERGE_REQUEST_TARGET_BRANCH_NAME" - - git fetch --quiet origin "+refs/heads/$target:refs/remotes/origin/$target" - - commit-check --branch - - | - head="${CI_MERGE_REQUEST_SOURCE_BRANCH_SHA:-$CI_COMMIT_SHA}" - shas=$(git rev-list "$CI_MERGE_REQUEST_DIFF_BASE_SHA..$head") || exit 1 - status=0 - for sha in $shas; do - commit-check --message --rev "$sha" --compact || status=1 - done - exit $status + - commit-check-ci ``` -- `GIT_DEPTH: "0"` turns shallow cloning off. -- A merge request pipeline fetches only the commit it runs on, so the job - fetches the target branch for the rebase check. A merge request from a fork - runs its pipeline in the fork, where `origin` is the fork: fetch from - `"$CI_MERGE_REQUEST_PROJECT_URL.git"` instead of `origin` there, so the - branch comes from the target project. -- In a merged results pipeline, `HEAD` is a merge commit GitLab made, and - `CI_MERGE_REQUEST_SOURCE_BRANCH_SHA` names the merge request's own last - commit. In a plain merge request pipeline that variable is empty and - `CI_COMMIT_SHA` is that commit. +Every check is listed under a heading of its own, and one failure fails the +job: + +```text +$ commit-check-ci +Branch + passed +Commit ccdfc043 added the login form +✖ CC001 message failed: added the login form + The commit message should follow Conventional Commits. See https://www.conventionalcommits.org + Suggest: Use (): , where is one of: feat, fix, docs, style, refactor, test, chore, perf, build, ci + Docs: https://commit-check.com/rules/#cc001 + +Commit 20119d2e fix: trim the user name + passed + +1 of 3 failed. +``` + +- `GIT_DEPTH: "0"` turns shallow cloning off, for this job only. The command + needs every commit of the merge request and the commit they start from. + With a clone that ends inside the merge request the job fails and names + this setting, rather than pass with commits unchecked. +- The command fetches the target branch itself, which + `require_rebase_target` ([CC202](../rules.md#cc202)) compares with. For a + merge request from a fork it fetches from the target project. A pipeline + that runs in a fork of a private project cannot fetch it: with that rule + set the branch check fails there, and without the rule the branch name is + checked as usual. +- In a merged results pipeline, `HEAD` is a merge commit GitLab made. The + checks stop at the merge request's own last commit. +- `rules` keeps the job to merge request pipelines. In any other pipeline the + command checks the branch and the last commit only, and says so. - The `python` image ships with git. A `-slim` image does not, and needs it installed first. +### Options + +Each check has an option, named after the +[Action's input](github-actions.md#inputs) and on or off by default as it is +there: + +| Option | Default | What it checks | +|---|---|---| +| `--message` | on | The message of every commit the request adds. | +| `--branch` | on | The name of the source branch, and `require_rebase_target` if it is set. | +| `--author-name` | off | The author name of every commit. | +| `--author-email` | off | The author email of every commit. | +| `--files` | off | The files every commit changes, against the [`[files]` rules](../rules.md#push-rules). | +| `--pr-title` | off | The title, with the message rules a one-line title can meet. | +| `--pr-body-ai-attribution` | off | The description, against the AI attribution rules. | + +An option alone switches its check on, and `=false` switches one off: + +```yaml + - commit-check-ci --author-email --branch=false +``` + ### Making a failed check block the merge Two things decide whether a failed check stops the merge request: @@ -114,28 +115,26 @@ Two things decide whether a failed check stops the merge request: ### Merge request title and description -GitLab passes both to the job, so they are piped in as they are. Add these -lines to the `script`, before the commit loop (its `exit` ends the script): +GitLab passes both to the job, so two options are all it takes: ```yaml - - printf '%s\n' "$CI_MERGE_REQUEST_TITLE" | commit-check --pr-title - - printf '%s\n' "$CI_MERGE_REQUEST_DESCRIPTION" | commit-check --ai-attribution-only + - commit-check-ci --pr-title --pr-body-ai-attribution ``` - `--pr-title` checks the title with the message rules a one-line title can meet: everything `--message` runs except a body (CC011), a sign-off (CC012) and an AI author (CC017). With squash merges the title is often the commit - message that lands. -- `--ai-attribution-only` checks the description against your + message that lands. A draft marker (`Draft:`, `[Draft]`, `(Draft)`) is not + part of the title that is checked. +- `--pr-body-ai-attribution` checks the description against your `ai_attribution` policy, and, when `[pull_request] ai_declaration_checkboxes` is set, that it ticks exactly one AI declaration box (CC501). GitLab task lists (`- [x]`, `* [x]`, `1. [x]`) are read like GitHub's. -- GitLab cuts `CI_MERGE_REQUEST_DESCRIPTION` to its first 2700 characters - (`CI_MERGE_REQUEST_DESCRIPTION_IS_TRUNCATED` is then `true`), so only that - part is checked. Put the AI declaration boxes near the top of the merge - request template, so a long description does not cut them off. To fail a - description that was cut rather than check part of it, add before the - description check: +- GitLab passes a job only the first 2700 characters of a description, so + only that part is checked, and the job says so when it happens. Put the AI + declaration boxes near the top of the merge request template, so a long + description does not cut them off. To fail a description that was cut + rather than check part of it, add before the `commit-check-ci` line: ```yaml - test "$CI_MERGE_REQUEST_DESCRIPTION_IS_TRUNCATED" != "true" || { echo "The description is over 2700 characters; GitLab passed only part of it"; exit 1; } @@ -158,54 +157,58 @@ pipelines: depth: full script: - pip install commit-check - - target="$BITBUCKET_PR_DESTINATION_BRANCH" - - git fetch --quiet origin "+refs/heads/$target:refs/remotes/origin/$target" - - commit-check --branch - - | - shas=$(git rev-list "$BITBUCKET_PR_DESTINATION_COMMIT..$BITBUCKET_COMMIT") || exit 1 - status=0 - for sha in $shas; do - commit-check --message --rev "$sha" --compact || status=1 - done - exit $status + - commit-check-ci ``` -- `depth: full` turns off the default clone depth of 50 commits. +- `depth: full` gives the step the pull request's whole history. With a clone + that ends inside the pull request the step fails and names this setting, + rather than pass with commits unchecked. - Bitbucket merges the destination branch into the pull request before the - step runs. The range stops at `BITBUCKET_COMMIT`, the pull request's own + step runs. The checks stop at `BITBUCKET_COMMIT`, the pull request's own last commit, so commits that only came in with that merge are not checked. The rebase check judges that commit too, not the merge. +- The output and the [options](#options) are the same as on GitLab. ### Pull request title and description Bitbucket gives the step the pull request's id but not its title or -description, so the step reads them from the Bitbucket API. Create a +description, so the command reads them from the Bitbucket API. Create a [repository access token](https://support.atlassian.com/bitbucket-cloud/docs/repository-access-tokens/) with the **Pull requests: Read** scope, store it as a secured repository -variable named `PR_READ_TOKEN`, and add to the `script`, before the commit -loop: +variable named `BITBUCKET_ACCESS_TOKEN`, and switch the two checks on: ```yaml - - >- - curl -fsS -H "Authorization: Bearer $PR_READ_TOKEN" - "https://api.bitbucket.org/2.0/repositories/$BITBUCKET_REPO_FULL_NAME/pullrequests/$BITBUCKET_PR_ID" - -o pr.json - - >- - python -c 'import json; pr = json.load(open("pr.json")); - open("title.txt", "w").write(pr["title"]); - open("description.txt", "w").write(pr["description"])' - - commit-check --pr-title < title.txt - - commit-check --ai-attribution-only < description.txt + - commit-check-ci --pr-title --pr-body-ai-attribution ``` -Reading the fields in a step of their own makes a failed API read fail the -step, instead of piping empty text into the check. `--pr-title` and -`--ai-attribution-only` work as in the +Without the variable, or with a token Bitbucket refuses, the two checks fail +and say why: a title that could not be read is never checked as empty text. +`--pr-title` and `--pr-body-ai-attribution` work as in the [GitLab section](#merge-request-title-and-description). Editing a pull request does not start a pipeline, so run the step again after an edit. ## Azure Pipelines +`commit-check-ci` knows GitLab's and Bitbucket's variables. Anywhere else it +checks the branch and the last commit only, so on Azure Pipelines, or a CI of +your own, the job calls `commit-check` itself. Commit Check is a Python +package with no runtime dependencies: any runner that can `pip install` can +run it. + +Two things are different from running it on your own machine, and the +example below handles both: + +- **The checkout can be a detached HEAD**, as it is on Azure, and then git + has no branch to report. `commit-check --branch` reads the name from the + CI's own variables instead, the pull request's source branch first, so the + job calls it as is. +- **A pull request has more than one commit.** `--rev` checks one commit, so + the job loops over the commits the pull request adds, as in + [Checking a range of commits](../example.md#checking-a-range-of-commits). + The loop needs the history those commits sit on, so the example turns + shallow cloning off. If the range cannot be read, the job fails rather than + passing with nothing checked. + ```yaml title="azure-pipelines.yml" trigger: none @@ -250,3 +253,21 @@ steps: [build validation branch policy](https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies#set-build-validation) on the target branch, and `System.PullRequest.SourceBranch` is only set for builds a branch policy started. +- Add `--author-name --author-email` to the `commit-check` call in the loop + to check each commit's author as well, and `--files` to check the files + each commit adds (configured in the `[files]` section). +- The branch check also covers `require_rebase_target` (CC202), which needs + the target branch in the clone as `origin/`. Without it the rule + reports itself as skipped (`rebase target 'main' not found`) and the job + passes. + +!!! note "On 2.18.2 or older" + + Releases before 2.18.3 read only GitHub's variables, so on a detached + checkout `--branch` judges `HEAD`, which is always allowed, and passes + whatever the branch is called. Pipe the name in instead: a value piped + into `--branch` on its own is the name it checks. + + ```console + $ echo "${SYSTEM_PULLREQUEST_SOURCEBRANCH#refs/heads/}" | commit-check --branch + ``` diff --git a/docs/guides/policies.md b/docs/guides/policies.md index 802b6e4..69ec4e5 100644 --- a/docs/guides/policies.md +++ b/docs/guides/policies.md @@ -243,7 +243,7 @@ ai_declaration_checkboxes = ["No AI tools were used", "If AI tools were used"] ```console $ gh pr view 42 --json body -q .body | commit-check --ai-attribution-only -✖ Commit rejected by Commit Check · 1 check failed +✖ Rejected by Commit Check · 1 check failed ✖ CC501 ai-declaration failed: - [ ] **No AI tools were used** in preparing this PR. (+1 more line) No AI declaration box is ticked diff --git a/docs/guides/pre-commit.md b/docs/guides/pre-commit.md index 17d48f2..5a42abd 100644 --- a/docs/guides/pre-commit.md +++ b/docs/guides/pre-commit.md @@ -8,7 +8,7 @@ Add Commit Check to `.pre-commit-config.yaml`: ```yaml title=".pre-commit-config.yaml" repos: - repo: https://github.com/commit-check/commit-check - rev: v2.22.0 + rev: v2.23.0 hooks: - id: check-message - id: check-branch @@ -68,7 +68,7 @@ Options can be passed as hook arguments, which keeps everything in one file: ```yaml title=".pre-commit-config.yaml" repos: - repo: https://github.com/commit-check/commit-check - rev: v2.22.0 + rev: v2.23.0 hooks: - id: check-message args: @@ -90,7 +90,7 @@ colon, and lets the commit through: ```yaml title=".pre-commit-config.yaml" repos: - repo: https://github.com/commit-check/commit-check - rev: v2.22.0 + rev: v2.23.0 hooks: - id: check-message args: [--fix] diff --git a/docs/rules.md b/docs/rules.md index 2c4021a..176359f 100644 --- a/docs/rules.md +++ b/docs/rules.md @@ -1204,7 +1204,7 @@ ai_declaration_checkboxes = ["No AI tools were used", "If AI tools were used"] ```console $ gh pr view 42 --json body -q .body | commit-check --ai-attribution-only -✖ Commit rejected by Commit Check · 1 check failed +✖ Rejected by Commit Check · 1 check failed ✖ CC501 ai-declaration failed: - [ ] **No AI tools were used** in preparing this PR. (+1 more line) No AI declaration box is ticked From f9872b8e58500516ecd805aa28ba18d42ae74982 Mon Sep 17 00:00:00 2001 From: Xianpeng Shen <3353385+shenxianpeng@users.noreply.github.com> Date: Thu, 19 Nov 2026 12:24:24 +0000 Subject: [PATCH 2/2] docs: name GitHub, GitLab and Bitbucket on the homepage Say where Commit Check runs in the hero facts, on the command line card, under the cards with a link to the GitLab and Bitbucket guide, in the FAQ and in the page description. --- docs/index.md | 18 +++++++++++------- docs/stylesheets/landing.css | 5 +++++ 2 files changed, 16 insertions(+), 7 deletions(-) diff --git a/docs/index.md b/docs/index.md index 39ef147..2afc4fb 100644 --- a/docs/index.md +++ b/docs/index.md @@ -4,7 +4,7 @@ hide: template: landing.html title: Commit Check seo_title: Commit Check — Commit policy as code for teams and AI agents -description: Commit policy as code for teams and AI agents. Messages, branches, authors and AI attribution, checked from your commit hook to every pull request. +description: Commit policy as code for teams and AI agents. Messages, branches, authors and AI attribution, checked from your commit hook to every pull request, on GitHub, GitLab and Bitbucket. --- @@ -64,7 +64,7 @@ description: Commit policy as code for teams and AI agents. Messages, branches,
  • MIT licensed, no account needed
  • Python 3.11 – 3.15 on Linux, macOS and Windows
  • Signed build provenance on every release
  • -
  • CLI and hook work with any Git host
  • +
  • GitHub, GitLab, Bitbucket and any Git host
  • @@ -87,7 +87,7 @@ conventional_branch = true - + + @@ -490,9 +491,12 @@ conventional_branch = true ??? question "Does it only work on GitHub?" - The CLI and the pre-commit hook run anywhere Git does — GitLab, Gitea, - Bitbucket, a local machine. The Action and the App are GitHub-specific - because they integrate with GitHub's check runs. + No. On GitLab CI and Bitbucket Pipelines one command, `commit-check-ci`, + checks every merge or pull request: see the + [GitLab and Bitbucket guide](guides/other-ci.md). The CLI and the + pre-commit hook run anywhere Git does — Gitea, Azure Pipelines, a local + machine. The Action and the App are GitHub-specific because they + integrate with GitHub's check runs. ??? question "Do I need Node.js?" diff --git a/docs/stylesheets/landing.css b/docs/stylesheets/landing.css index ee0a3bf..a219ae7 100644 --- a/docs/stylesheets/landing.css +++ b/docs/stylesheets/landing.css @@ -800,6 +800,11 @@ font-weight: 600; } +/* A second link under the first: the two read as one block. */ +.md-typeset .cc-more-link--next { + margin-top: 8px; +} + /* On a phone the five cards become a list of rows: the icon, the name and what it is for. The details are one tap away on the guide. */ @media screen and (max-width: 599px) {