validate-repo.sh: flag a missing Agent label at onboarding #376
Labels
No labels
Agent
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
joshtronic/igor#376
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up from #375 (greenlight gate fail-closed).
bin/validate-repo.shprints the onboarding readiness checklist but doesn't check whether the repo has the customAgentlabel. sharktankdb.com was onboarded without it, which is what let the pre-#375 gate fail open (Forgejo ignores alabels=Agentfilter naming a label the repo lacks).With #375 merged, a missing
Agentlabel is now safe (the grind claims nothing there) — but it's a silent footgun: a repo meant to be agentic that lacks the label just does no issue work, with no signal. Add anAgent-label presence check to the validation checklist so onboarding flags it.Low priority — the fail-closed fix removed the danger; this is the "so you notice" half.