Why
The workflows page showed the file path and job IDs, so a reader had to open the YAML comments to learn what a workflow was for. This is the identity and description slice of #138.
What changes
- Add top-level
name:anddescription:to workflows, defaulting the name to the file stem (verify.yaml→verify). - Add job
name:anddescription:, defaulting the name to the job ID. - Validate both as trimmed, single-line text, with an 80-byte name limit and a 500-byte description limit.
- Pin names and descriptions with a queued run, so editing a workflow later does not rewrite the pages of runs that already happened.
- Show the metadata on the workflows page, the run page, the runs list, the repository overview, and change check lists.
- Document the fields in the workflow reference.
- Add a “What a workflow cannot express” section to the workflow reference.
- State in
docs/workflows.mdthat CI jobs are independent and unordered; only a local run uses declaration order.
Checks
git diff --checkgo vet -tags sqlite_fts5 ./...vole workflow run verify— formatting, vet, build, licenses, govulncheck, packaging, links, and race tests all passed.
Part of #138. This does not close the tracking issue.