ci(dependabot): bootstrap dependabot-gate check for branch-protection activation - #115
Merged
Merged
Conversation
…ion can pin it Documents the preflight bootstrap requirement; this PR's own run is the first dependabot-gate check-run on the plugin, which lets enable-branch-protection.sh pin the context (its preflight fail-closes on a never-published context). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bootstrap the dependabot-gate check on the plugin repo
Activation step.
enable-branch-protection.sh's preflight fail-closes when a context has never published a check-run (pinning it would deadlock merges), sodependabot-gatecannot be pinned required on this repo untildependabot-gate.ymlhas run at least once. It was added by #113, so it never ran on #113 itself, and there've been no plugin PRs since. This PR's ownpull_request_targetrun is that firstdependabot-gatecheck-run; once it reports, the branch-protection script can pin the context, completing plugin-side activation. The workspace side is already live.The change itself is a one-line documentation note in the gate workflow header + a changelog fragment. CI/governance only, no distributed content, no version bump.
author: claude
standing_directives: operator instruction 2026-08-18 ("run the branch protection script and activate the feature"); directive #6 Tier-1/2; fragment-only changelog; signed commits
tier: 2
cross_check: PROCEED — Grok (xAI, distinct family), 1 round: "VERDICT: PROCEED — comment-only header plus a standard changelog fragment; on/permissions/jobs are untouched, so the workflow is behavior-identical." No concerns.
post_condition: dependabot-gate.yml YAML valid; release-consistency PASS; this PR's dependabot-gate run bootstraps the context for pinning
mcp_coverage_gap: none
contributor_rights: OWNER-AUTHORED
operator_reserved: no — operator-directed activation
plugin_affected: self (CI workflow doc note only)
readme_refresh_status: README unaffected (no release)
🤖 Generated with Claude Code