[step-names] Align step names in BinEval evals job with glossary/consistency

Open Beginner friendly
#73,985 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
64/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, go
Domain
ci-cd

Research direction

Open pkg/workflow/evals_steps.go and find the step name string Execute BinEval Decisions near line 78, then compare it with the sibling Parse BinEval results near line 104. Change the capitalization of the trailing noun in the Go source, then run make recompile so the generated .lock.yml files pick it up. Done when the new name appears in the regenerated lock files and the existing tests pass.

Written by the indexing model from the issue text.

Description

cookie maintenance step-naming
Step Name Alignment Issues

Found in: pkg/workflow/evals_steps.go (affects all ~168 generated .lock.yml files with an evals: block, e.g. .github/workflows/ab-testing-advisor.lock.yml, .github/workflows/ace-editor.lock.yml, .github/workflows/agentic-token-audit.lock.yml)

  • Priority: Medium
  • Current step names: Execute BinEval Decisions (pkg/workflow/evals_steps.go:78) and Parse BinEval results (pkg/workflow/evals_steps.go:104)
  • Why it conflicts: These two steps belong to the same BinEval evals feature and follow the shared Verb BinEval <noun> shape, but the trailing noun is capitalized inconsistently: Decisions is Title Case while the sibling step uses lowercase results. Every other common-noun suffix used elsewhere in step names (results, evaluations, summary, metadata, etc.) is lowercase unless it is a proper noun/glossary term (e.g. MCP Gateway, Safe Outputs). Decisions is not a glossary term, so Title-casing it breaks the established convention and reads as an inconsistency between two adjacent steps in the same job.
  • Suggested replacement: Rename Execute BinEval Decisions to Execute BinEval decisions to match the lowercase-noun convention used by its sibling Parse BinEval results.

Both steps are new since the last alignment run (not present in the prior manifest scan) and are generated from a single source location, so the fix is a one-line rename in evals_steps.go:78 with a make recompile to propagate to all affected lock files.

Generated by 📋 Step Name Alignment · claude · agent · ~104 AIC · ⌖ ~1 AIC · ⊞ 4.4K · ◷

  • expires on Nov 3, 2026, 8:02 PM UTC-08:00
Dominant language
Go
Stars
5.6k
Forks
615
Avg merge
4h 51m
Merged PRs (30d)
778

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/gh-aw

All issues in github/gh-aw

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.