Skip to content

ci(sync-docs): create 'automated' label before opening sync PR - #21

Draft
Sbussiso wants to merge 1 commit into
masterfrom
ci-fix/28716053829
Draft

ci(sync-docs): create 'automated' label before opening sync PR#21
Sbussiso wants to merge 1 commit into
masterfrom
ci-fix/28716053829

Conversation

@Sbussiso

@Sbussiso Sbussiso commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

Root cause

The Sync Docs workflow run #8 (run 28716053829) failed at the Open or update sync PR step:

could not add label: 'automated' not found
##[error]Process completed with exit code 1.

The workflow tries to label its auto-sync PR with automated, but that label does not exist in this repo — only the default GitHub labels are present (bug, documentation, enhancement, etc.).

Fix

Ensure the automated label exists before opening the PR:

gh label create automated --description "Automated PR opened by a GitHub Actions workflow" --color 0E8A16 2>/dev/null || true

The 2>/dev/null || true makes the create idempotent and non-fatal — if the label already exists (e.g. on subsequent runs) the line is a no-op, and PR creation still proceeds.

Verification

  • Labels currently on the repo (confirmed): bug, documentation, duplicate, enhancement, good first issue, help wanted, invalid, question, wontfix — no automated.
  • After this merges, the next scheduled/hand-triggered Sync Docs run will create the label and open the PR cleanly.

Notes

Opened by Hermes coder as part of automated CI triage of run #28716053829. Draft until reviewed/merged.

The Sync Docs workflow run #8 failed because it tried to add the
'automated' label to the auto-sync PR, but that label does not exist
in the repo (only the default GitHub labels are present).

Fix: ensure the label exists before PR creation. gh label create
is idempotent here (guarded with 2>/dev/null || true so a subsequent
run that finds the existing label won't fail).

Closes CI failure on commit a77ae36.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants