codex-bot-andresmgsl/rig
1
0
Fork 0
forked from heavy-duty/rig
Code Pull requests Activity

docs: make the bootstrap trim idempotent — swallow delete of an already-gone label

Browse source 
All three bot reviewers flagged it: gh label delete is not an upsert, so a
second run of the safe-to-run block errored on the trim lines. Loop + '|| true'.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
dan-claude-bot 2026-07-18 18:04:51 +00:00
parent e07a8ab567
commit ca37eb8450
1 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
LABELS.md
View file

@ -76,6 +76,9 @@ gh label create "scope:runner" --color C5DEF5 --description "runner-*
gh label create "scope:coolify" --color C5DEF5 --description "coolify-* — Coolify and backup install" --force gh label create "scope:coolify" --color C5DEF5 --description "coolify-* — Coolify and backup install" --force
gh label create "scope:db" --color C5DEF5 --description "db.sh — dump/restore" --force gh label create "scope:db" --color C5DEF5 --description "db.sh — dump/restore" --force
gh label create "scope:installer" --color C5DEF5 --description "install.sh — how rig lands on a machine" --force gh label create "scope:installer" --color C5DEF5 --description "install.sh — how rig lands on a machine" --force
gh label delete duplicate --yes; gh label delete invalid --yes; gh label delete question --yes # delete is not an upsert: a label that is already gone exits non-zero. Swallow
gh label delete wontfix --yes; gh label delete "help wanted" --yes; gh label delete "good first issue" --yes # that, so this block converges on re-run instead of erroring after first success.
for L in duplicate invalid question wontfix "help wanted" "good first issue"; do
gh label delete "$L" --yes 2>/dev/null || true
done
``` ```