Skip to content

[refactoring] Extract shared gh-cli-proxy.md component (122 workflow duplicates) #54136

Description

@github-actions

Summary

122 workflows set both tools.cli-proxy: true and tools.github.mode: gh-proxy together (206 and 155 workflows set them individually). The existing shared/gh.md component only covers tools.github.mode: gh-proxy (used by 15 workflows) and does not bundle cli-proxy: true, so the pairing is still duplicated across 122 files.

Evidence

Example: ci-coach.md lines 21 (cli-proxy: true) and 23 (mode: gh-proxy), directly adjacent under tools:. Same pattern repeats across 121 other workflows.

Proposal

Create a new shared component shared/gh-cli-proxy.md (kept separate from shared/gh.md to avoid changing behavior for shared/gh.md's 15 existing consumers):

---
tools:
  cli-proxy: true
  github:
    mode: gh-proxy
---

Consumers replace the inline block with:

imports:
  - shared/gh-cli-proxy.md

Impact

  • ~122 workflows affected
  • ~300 lines of duplicated YAML removed
  • Reduces risk of the two settings drifting independently (e.g. one workflow enabling cli-proxy without gh-proxy mode, or vice versa, by accident)

Migration plan

  1. Confirm whether shared/gh.md's 15 existing consumers would be compatible with cli-proxy: true added (if so, consider extending shared/gh.md instead of creating a new file).
  2. Create shared/gh-cli-proxy.md bundling both settings (safest option regardless).
  3. Migrate the 122 workflows using both settings adjacently.
  4. Recompile and diff .lock.yml files to confirm no behavioral change.

Priority

Medium — appears in 122 workflows (high count) but requires a compatibility check against the existing shared/gh.md component before rollout, so extraction complexity is higher than the other two candidates.

Generated by 🔍 Workflow Skill Extractor · auto · 86 AIC · ⌖ 5.54 AIC · ⊞ 7.4K ·

  • expires on Aug 21, 2026, 8:01 PM UTC-08:00

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions