Skip to content

docs: add maintainer reference for the CI/CD workflows#90

Merged
Reefact merged 3 commits into
mainfrom
claude/workflow-docs
Jul 10, 2026
Merged

docs: add maintainer reference for the CI/CD workflows#90
Reefact merged 3 commits into
mainfrom
claude/workflow-docs

Conversation

@Reefact

@Reefact Reefact commented Jul 10, 2026

Copy link
Copy Markdown
Owner

Summary

Add a maintainer-facing reference under maintainers/workflows/ that documents every GitHub Actions workflow — an index page plus one page per workflow, in English (canonical) and French. It captures the why and the "handle with care" traps that the YAML comments hold line-by-line, so a maintainer knows what not to change before touching a workflow.

Type of change

  • Documentation

Changes

  • Add maintainers/workflows/README.en.md / README.fr.md — the index: cross-cutting conventions (SHA-pinned actions, least-privilege permissions, per-job timeouts, concurrency, weekly scheduled scans, fork-safety, required checks as the real gate) and a themed table of contents.
  • Add one page per workflow (EN + FR), following a common template — What it is for · When it runs · How it runs · Permissions & security · Handle with care · Related:
    • ci, sonar, analyzers, commit-lint (build & quality)
    • codeql, dependency-review, scorecard (security & supply chain)
    • release, release-dryrun (release)
    • dependabot-automerge (dependency maintenance)
  • The release / release-dryrun pages link to the existing maintainers/ReleaseDryRun.*.md guide, and the analyzers page links to maintainers/adr/0001-lock-the-analyzer-roslyn-floor.md, rather than duplicating them.
  • No workflow YAML or source is changed.

Testing

  • dotnet build FirstClassErrors.sln
  • dotnet test FirstClassErrors.sln
  • Analyzer tests pass (FirstClassErrors.Analyzers.UnitTests)

Not applicable — documentation only, no code touched. All relative links in the new pages were validated to resolve.

Documentation

  • README / doc/ updated
  • French translation updated — every page ships in EN (canonical) and FR

Related issues


Generated by Claude Code

claude added 3 commits July 10, 2026 23:16
Add a maintainer-facing reference under maintainers/workflows/ documenting
every GitHub Actions workflow. A main index (README) presents the cross-cutting
conventions (SHA-pinned actions, least-privilege permissions, per-job timeouts,
concurrency, weekly scheduled scans, fork-safety, and required checks as the
real gate) and links, grouped by theme, to one page per workflow.

Each per-workflow page follows a common template: what it is for (pedagogical),
when it runs, how it runs, permissions and security, and a "handle with care"
section capturing the non-obvious decisions that must not be changed without
understanding why. The release and analyzers pages link to the existing
ReleaseDryRun guide and ADR 0001 rather than duplicating them.

All pages are provided in English (canonical) and French, per CONTRIBUTING.md
and the repository language policy.
Wire the new workflow pages into the maintainer documentation so no page is
orphaned:

- Add a maintainers/ landing index (README.md + README.fr.md) that GitHub
  auto-renders, listing the workflow reference, the release dry-run runbook, and
  the ADR log.
- Rename the workflow index from README.en.md to README.md so it auto-renders
  when browsing maintainers/workflows/, and update the inbound links.
- Add breadcrumbs from the workflow reference up to the maintainers index, and
  reciprocal links from the ReleaseDryRun runbook to the release and
  release-dryrun reference pages (plus a language switcher on the runbook).

No content in the ADR is changed; it stays a standalone decision record, now
linked from the index and the analyzers page.
The adoption note pointed ADRs at doc/adr/, but the repository keeps them under
maintainers/adr/ (where ADR 0001 lives). Align the guide with the actual
location.
@Reefact Reefact enabled auto-merge July 10, 2026 23:30
@Reefact Reefact merged commit b937de0 into main Jul 10, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants