ci(policy): exempt dependabot pull requests from body validation - #3
Merged
Merged
Conversation
benjiwagner
force-pushed
the
ci/exempt-dependabot-body-validation
branch
from
July 20, 2026 08:03
5485ec7 to
33b086c
Compare
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
1 participant
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.
Summary
dependabot[bot]from the required body-section validation while keeping branch, title, and commit-header rules fully enforced.Context
Dependabot version updates were enabled on n8n-nodes-crm on 2026-07-20. Dependabot cannot author the required Summary/Context/Validation/Impact body sections, so its pull requests would permanently fail the required
repository-policycheck under the zero-bypass integrity ruleset. Its branch names were already exempted; commit headers and titles pass through the configuredchore(deps)prefix.Validation
bash -nclean andvalidate.sh --self-testpasses on the patched script.Impact and rollback
After merge, caller workflows in knowledge-base and n8n-nodes-crm need their pinned reusable-workflow SHA bumped to this commit (tracked in Linear CUS-89). Roll back by reverting the squash commit and restoring the previous pin.