REPOMATIC-BROKEN-LINKS(1) REPOMATIC-BROKEN-LINKS(1)

repomatic broken-links - Manage broken links issue lifecycle

repomatic broken-links [OPTIONS]

Manage the broken links issue lifecycle.

Combines Lychee and Sphinx linkcheck results into a single "Broken links" issue. Creates, updates, or closes the issue based on results.

Requires the gh CLI to be authenticated.

In GitHub Actions, most options are auto-detected:
- --repo-name defaults to $GITHUB_REPOSITORY name component.
- --body-file defaults to ./lychee/out.md when --lychee-exit-code is set.
- --output-json defaults to ./docs/_linkcheck/output.json if it exists.
- --source-url is composed from $GITHUB_SERVER_URL, $GITHUB_REPOSITORY,

and $GITHUB_SHA when --output-json is set.

Exit code from lychee (0=no broken links, 2=broken links found).
Path to the issue body file (lychee output).
Path to Sphinx linkcheck output.json file.
Base URL for linking filenames and line numbers in the Sphinx report. Example: https://github.com/owner/repo/blob/<sha>/docs
Repository name (for label selection). Defaults to $GITHUB_REPOSITORY name component.
Show this message and exit.

Exit code from lychee (0=no broken links, 2=broken links found).
Path to the issue body file (lychee output).
Path to Sphinx linkcheck output.json file.
Base URL for linking filenames and line numbers in the Sphinx report. Example: https://github.com/owner/repo/blob/<sha>/docs
Repository name (for label selection). Defaults to $GITHUB_REPOSITORY name component.
Show this message and exit.

0
Success.
1
A runtime error, or an aborted prompt (Ctrl-C, a declined confirmation).
2
A usage error: unknown option, invalid value, missing operand, or an unparsable configuration file.

In GitHub Actions, with every default auto-detected

repomatic broken\-links \-\-lychee\-exit\-code 2

Explicit options

repomatic broken\-links \-\-lychee\-exit\-code 2 \-\-body\-file ./lychee/out.md \-\-repo\-name "my\-repo"

Kevin Deldycke

2026-09-14 7.15.1.dev0