ci: recover the bp-required directive dropped from #2660 (lint-required-context) #2663
Reference in New Issue
Block a user
Delete Branch "fix/2660-recover-bp-directive"
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?
#2660 merged with the new e2e job but WITHOUT the
# bp-required: pending #2619directive — I pushed the lint fix moments after the queue merged, so it landed on the closed branch (the push-after-merge pattern from #2641). main now hase2e-staging-workspace-requestswithout the directive the Tier-2g lint-required-context-exists-in-bp check requires.This adds just that one-line directive (matching the concierge job's
# bp-required: pending #2430pattern). One commit, single file.🤖 Generated with Claude Code
APPROVED: reviewed head
c46e629644. Diff is exactly the one-line # bp-required: pending #2619 directive above e2e-staging-workspace-requests, matching the existing pattern and restoring the lint-required-context-exists-in-bp gate without changing job behavior. CI / all-required and the targeted lint are green; remaining reds are review/SOP or unrelated lifecycle contexts.