Skip to content

ci: give every job a Title Case display name - #155

Merged
kyle-sexton merged 1 commit into
mainfrom
ci/name-every-job
Nov 14, 2026
Merged

kyle-sexton merged 1 commit into
mainfrom
ci/name-every-job

Conversation

@kyle-sexton

Copy link
Copy Markdown
Member

No related issue: display names for this repository's workflow jobs, found by running the org naming lint over every repository.

Summary

Every job in this repository's own workflows now has a Title Case display name that is the Title Case of its job id. Check names change with it, for example pr-run-checks / Check becomes PR Run Checks / Check. CI Status stays the only required check.

Fix

Verification

  • naming-lint --mode enforcing from melodic-software/standards main on this branch: no job-name or step-name finding in the files this repository owns.
  • Searched this repository for each old job name and for <job id> / : no script, test or filter reads one.
  • Left out: a local test run, because the change is display names only and CI runs on this pull request.

Related

🤖 Generated with Claude Code

Each job's display name is the Title Case of its job id, the form the
org naming lint checks.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@kyle-sexton
kyle-sexton marked this pull request as ready for review November 14, 2026 10:37
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-14T10:38:50.614748Z c9853e9 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions

Copy link
Copy Markdown

claude-security-review reviewed c9853e9c8fd70ea29789aba71d797a8733c44ce1: 0 finding(s), 0 as inline comments.

No security issues found.

The diff changes only display names: one new name: on the pr-automerge-dependabot job, and renamed job and step name: fields in pr-require-checks.yml. I read the full diff and found no change to any of these:

  • permissions:
  • if: conditions
  • triggers
  • run: commands
  • action pins
  • secrets
  • the trusted-actor, kill-switch or merge-hold controls

The skip gate does not apply here because this is a workflow change, so I read it in full.

I searched the repo for references to the old job names ("Shell (", "Manifests (", "Offline links", "Spelling (", "Docs (internal"). Nothing outside the diff itself uses them, so no required-check or name-matching logic depends on them. CI Status is the single required check, and the diff does not touch it.

No manifest <field> items were hit.

critical-findings: 0

@github-actions

Copy link
Copy Markdown

claude-review reviewed c9853e9c8fd70ea29789aba71d797a8733c44ce1: 0 finding(s), 0 as inline comments.

No findings. I read the diff and the PR context, and checked the workflow file at head.

  • Required check: CI Status is unchanged (name: CI Status, still needs: every renamed job), so the single required check keeps its name.
  • Old names: I searched the repo for the old job names (Shell (shellcheck, Manifests (JSON, Offline links, Spelling (typos, Docs (internal). They appear only in the diff file, so no script, test or filter reads them.
  • Scope of the edit: only name: values change in .github/workflows/pr-automerge-dependabot.yml and .github/workflows/pr-require-checks.yml. No job ids, needs:, if: conditions or step commands change.
  • Not done: I did not run the naming lint or the workflows, so the lint-clean claim in the PR body is author-claimed and unverified by me.
  • Observation, not a finding: the psscriptanalyzer job keeps PowerShell (PSScriptAnalyzer), which is not the Title Case of its job id, although the title says "every job". The PR body says the lint reports no job-name finding, so I take it as intentional.
  • Closing issue: none (the PR uses the "No related issue" escape), so there are no acceptance criteria to check.
  • Manifests: no plugin manifests changed, so there are no manifest <field> lines.

Verifier dropped 0 of 0 candidates.

@kyle-sexton
kyle-sexton merged commit 352bf93 into main Nov 14, 2026
14 checks passed
@kyle-sexton
kyle-sexton deleted the ci/name-every-job branch November 14, 2026 10:44
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.

1 participant