Repository navigation
[step-names] Align "Copy safe outputs" step name capitalization with Safe Outputs glossary term #20665
Description
Step Name Alignment Issues
Found in: all compiled .lock.yml files (159 occurrences across ~159 workflows)
Summary
The step name Copy safe outputs uses lowercase "safe outputs", inconsistent with all other step names that reference the Safe Outputs feature. Per the project glossary, "Safe Outputs" is a product/feature name and should be consistently capitalized.
Issue Identified
[High Priority] Capitalization Inconsistency: "Copy safe outputs" → "Copy Safe Outputs"
Current step name (159 occurrences):
Copy safe outputs
Issue:
All other step names that reference the Safe Outputs feature use proper capitalization, but this compiled step uses lowercase:
| Step Name | Capitalization |
|---|---|
Copy safe outputs |
❌ lowercase |
Process Safe Outputs |
✅ capitalized |
Upload Safe Outputs assets |
✅ capitalized |
Write Safe Outputs Config |
✅ capitalized |
Generate Safe Outputs MCP Server Config |
✅ capitalized |
Start Safe Outputs MCP HTTP Server |
✅ capitalized |
Upload Safe Output Items Manifest |
✅ capitalized |
Glossary reference: The glossary defines Safe Outputs as: "Pre-approved actions the AI can take without elevated permissions." This is a named feature/product that warrants consistent capitalization.
Suggested fix:
- Change
Copy safe outputs→Copy Safe Outputs
Agentic Task Description
To fix this step name:
- Find the source — This step name is generated by the gh-aw compiler, likely from a shared template or action. Search the actions folder:
grep -r "Copy safe outputs" .github/ --include="*.sh" --include="*.yml" --include="*.go"
- Apply the fix — Update the source template/action that generates this step name
- Recompile all workflows — Run
gh aw compileon all affected workflows, or trigger a bulk recompile - Verify — Confirm all
.lock.ymlfiles now useCopy Safe Outputs
Related Files
- Compiled workflows:
.github/workflows/*.lock.yml(159 files affected) - Project glossary:
docs/src/content/docs/reference/glossary.md#safe-outputs
Priority
This issue is High Priority because it affects 159 compiled workflow files and conflicts with the established glossary term capitalization enforced consistently in all other step names.
AI generated by Step Name Alignment for daily maintenance
Generated by Step Name Alignment · ◷
- expires on Mar 14, 2026, 12:28 PM UTC
Activity