Skip to content

docs: explain CI triggers, jobs, and caches - #11506

Open
Roasbeef wants to merge 4 commits into
lightningnetwork:masterfrom
Roasbeef:docs-ci-runs
Open

Roasbeef wants to merge 4 commits into
lightningnetwork:masterfrom
Roasbeef:docs-ci-runs

Conversation

@Roasbeef

@Roasbeef Roasbeef commented Nov 5, 2026

Copy link
Copy Markdown
Member

In this PR, we add docs/ci-runs.md to explain which CI workflows run for pull requests, merge-queue entries, and nightly master runs. The document maps each tier to its jobs, explains how CI result handles skips and failures, and describes the shared Go, Docker image, and lint analysis caches.

The guide also covers label controls, the rebase step, failure artifacts, and the release-related workflows, so a contributor can find the relevant check without reading the full workflow YAML. The contribution guide links to the new document.

Anchor: 7669a85c04.

Diagrams: one trigger/tier flowchart and one ci-result sequence diagram. Both rendered locally with mmdc syntax checking; the sandbox cannot launch Chrome, so final rendering is verified on the pushed GitHub page.

Known gaps: the guide summarizes the main validation and release workflows; the repository-assistant workflows are indexed without internal detail.

In this commit, we add docs/ci-runs.md to explain which CI workflows run
for pull requests, merge-queue entries, and nightly master runs. The
document maps each tier to its jobs, explains how the CI result check
handles skips and failures, and describes the shared Go, Docker image,
and lint analysis caches.

The guide also covers label controls, the PR rebase step, failure
artifacts, and the release-related workflows, so a contributor can find
the relevant check without reading the full workflow YAML. The
contribution guide links to the new document.
@github-actions github-actions Bot added ci-hold CI is held; remove this label to run CI severity-low Best-effort review labels Nov 5, 2026
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown

🟢 PR Severity: LOW

docs/* | 3 files | 167 lines changed

🟢 Low (3 files)
  • docs/ci-runs.md - new documentation explaining CI triggers, jobs, and caches
  • docs/code_contribution_guidelines.md - single link added to new doc
  • docs/release-notes/unreleased/11506.md - release note entry

Analysis

This PR only touches documentation files (docs/*) with no changes to Go source, protocol definitions, or any critical/high-risk packages. File count (3) and line count (167) are both well under the thresholds that would trigger a severity bump. Classified as LOW — best-effort review is sufficient.


To override, add a severity-override-{critical,high,medium,low} label.

Add a quick reference, a tier selection flowchart, a PR lifecycle state
diagram, a tier by job matrix, and flowcharts for releasing a held PR,
for how CI result decides, for the nightly report and for the caches.
End with a troubleshooting table.
The release notes check only accepts the headings of the template, so
the fragment would fail it once CI runs.
@Roasbeef Roasbeef removed the ci-hold CI is held; remove this label to run CI label Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

severity-low Best-effort review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants