Repository navigation
Fix CLI sync workflow #2080
Description
Summary
The CLI sync workflow is failing and not producing the expected synchronization outcomes.
Workflow links
- Workflow definition: https://github.com/github/awesome-copilot/blob/staged/.github/workflows/cli-for-beginners-sync.md
- GitHub run list: https://github.com/github/awesome-copilot/actions/workflows/cli-for-beginners-sync.lock.yml
Scope
- Reproduce failure and identify the precise break point
- Update workflow/job logic to restore sync behavior
- Validate outputs and downstream compatibility
- Capture any required version/config constraints in docs
Acceptance criteria
- Workflow passes on
staged - Sync output matches expected repository state changes
- No known blocking runtime or permission errors remain
- Documentation reflects current prerequisites and behavior
Parent
Part of #2076
Activity
Upgrade agentic workflows from gh-aw v0.72.1 to v0.80.9
Upgrade agentic workflows from gh-aw v0.72.1 to v0.80.9 (#2092)
ayangupt commentedon Jun 24, 2026
Resolved by #2092 (gh-aw
v0.72.1→v0.80.9upgrade, merged tostagedand promoted tomain).Root cause: the same
safe_outputs"Failed to apply bundle" defect as #2077 under v0.72.1. The upgrade recompiles the workflow to v0.80.9.Evidence:
safe_outputs✅. The safe-output was empty (no content drift): nothing needed syncing, so no PR was opened — the correct no-op outcome when the synced content already matches.schedule@mainruns on v0.72.1 were failing (e.g. 27395958887).v0.80.9onstaged/main.Acceptance criteria:
The next scheduled run will reconfirm in production. Closing as completed; reopen if a scheduled run regresses.
Upgrade agentic workflows from gh-aw v0.72.1 to v0.80.9