Skip to content

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

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 09:18
@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-14T09:20:49.103114Z 9669be4 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-review reviewed 9669be4c8e6eb5ace82df62a6eba30441210dc92: 0 finding(s), 0 as inline comments.

No findings. The change only sets or renames three job display names, and I found nothing that depends on the old names.

I read the full diff and the PR context and grepped the repository for the old names. Marketplace contracts and Offline links appear nowhere else. The remaining validate-marketplace and pr-automerge-dependabot matches are the job IDs and script file names, which did not change. The CI Status job still lists validate-marketplace and lychee by ID in needs:, so the required-check wiring is unaffected.

  • Closing issue: none; the PR states "No related issue" with a reason, so there are no criteria to check.
  • Manifests: the diff touches no plugin.json or marketplace.json, so no manifest lines apply.
  • Rules: .claude/rules/pr-body-contract.md is the only rule file. The PR title and body follow it.
  • Not verified: I did not run npm test, npm run validate or the naming lint. The PR's claimed lint result is author-claimed and unverified by me.

Verifier dropped 0 of 0 candidates.

@github-actions

Copy link
Copy Markdown

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

No security findings.

The PR changes only the display name: of three jobs: PR Automerge Dependabot in pr-automerge-dependabot.yml, and Validate Marketplace and Lychee in pr-require-checks.yml. I changed nothing and posted nothing.

  • It does not touch permissions:, if: conditions, triggers, steps, secrets, or action pins.
  • It does not change the trust controls: the trusted-trigger check, the token scope, the kill switch, or the merge-hold scripts. pr-require-checks.yml is a hold path, but only job display names changed there. The ci-status hold steps are untouched.
  • No file in the repo refers to the old names "Marketplace contracts" or "Offline links". I found no consumer of the job names in the tree, and none of the three new names appears anywhere else.
  • Check names in a branch ruleset live outside the repo, so I could not check them. If a ruleset requires the old names, the renamed checks would never report and merges would be blocked. That blocks rather than bypasses, so it is not a security issue. It is only an operational point to confirm.
  • No plugin manifests or instruction surfaces are involved. The skip-gate "no security-relevant surface" condition holds, so I did not run a deeper review.

critical-findings: 0

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