Skip to content

[step-names] Align capitalization of compiler-generated "Upload safe output items" step name #22264

@github-actions

Description

@github-actions

Step Name Alignment Issue

Found in: 169 .lock.yml workflows (compiler-generated step)

Summary

The compiler-generated step Upload safe output items uses inconsistent capitalization compared to its companion step Upload Safe Outputs Assets and the broader "Safe Outputs" naming convention used throughout the codebase. This affects every workflow that uses safe outputs.

Issue Identified

[High Priority] Capitalization inconsistency: "Upload safe output items" → "Upload Safe Output Items"

Current step name (169 workflows):

Upload safe output items
```

**Companion step (24 workflows) — correctly title-cased:**
```
Upload Safe Outputs Assets
```

**Previous name in this codebase (now renamed):**
```
Upload Safe Output Items Manifest
```

**Issue:**
The step name `Upload safe output items` breaks the established capitalization pattern for Safe Outputs related steps. All other Safe Outputs steps use title case for "Safe Output(s)":

- `Write Safe Outputs Config`
- `Write Safe Outputs Tools`
- `Process Safe Outputs`
- `Upload Safe Outputs Assets` ← companion upload step in the same job
- `Copy Safe Outputs`
- `Start Safe Outputs MCP HTTP Server`
- `Generate Safe Outputs MCP Server Config`
- `Setup Safe Outputs Custom Scripts`

The lowercase `safe output items` is inconsistent with all of these. The previous name `Upload Safe Output Items Manifest` used correct title case.

**Suggested fix:**
```
"Upload safe output items" → "Upload Safe Output Items"

Agentic Task Description

This is a compiler-generated step — the fix must be made in the gh-aw compiler source, not in individual .lock.yml files:

  1. Locate the template in the compiler source that generates the step name Upload safe output items
  2. Update the template to produce Upload Safe Output Items
  3. Recompile all affected workflows — run gh aw compile --all or equivalent to regenerate the 169+ .lock.yml files
  4. Verify that all compiled lock files now show Upload Safe Output Items

Related Files

  • Compiler source: look for Upload safe output items or safe-output-items template
  • Project glossary: docs/src/content/docs/reference/glossary.md
  • Example compiled file: .github/workflows/agent-performance-analyzer.lock.yml

Priority

This issue is High Priority — it affects 169 workflows and breaks the established Safe Outputs capitalization convention. Since it is compiler-generated, a single fix at the source level resolves all instances.


AI generated by Step Name Alignment for daily maintenance

Note

**🔒 Integrity filter blocked 1 item**

The following item were blocked because they don't meet the GitHub integrity level.

  • #unknown search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Step Name Alignment ·

  • expires on Mar 24, 2026, 12:27 PM UTC

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions