Skip to content

fix: ensure autopublish labels exist before using them #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
avrabe merged 1 commit into from
Apr 26, 2026
Merged

fix: ensure autopublish labels exist before using them #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .github/workflows/blog-autopublish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,16 @@ jobs:
git config user.name "github-actions[bot]"
git config user.email "41898282+github-actions[bot]@users.noreply.github.com"

- name: Ensure labels exist
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
# `gh label create --force` upserts (creates or updates), so this
# step is idempotent and immune to a label being deleted manually.
gh label create autopublish --color 6c8cff --description "Auto-publish PR opened by the daily cron" --force
gh label create autopublish-status --color 22d3ee --description "Pinned status issue for the auto-publish cron" --force
gh label create autopublish-failure --color f87171 --description "Auto-publish workflow failed on this run" --force

- name: Scan drafts
id: scan
run: |
Expand Down
Loading