docs(dev-cycle): #126 — add §4.5.6 Workflow security hardening#525
Merged
Conversation
Captures the durable CI-author principles the #114 audit asked for: input handling (os.environ over shell interpolation, the OWASP A03 hazard), trigger choice (pull_request vs pull_request_target), permissions scoping (least privilege at workflow, widen per-job), and required-check deadlocks (paths: + branch-protection interaction, workflow_dispatch as the escape hatch). Anchor case studies link to the existing inline notes so this section stays an index rather than duplicating workflow-specific detail that should live next to the workflow. Pure additive doc change — new subsection between §4.5.5 and §4.6, no existing content modified. Risk L1. Closes #126 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
Closes #126.
Adds a new subsection §4.5.6 Workflow security hardening to
docs/DEV_CYCLE.mdcapturing the durable CI-author principles the #114 audit asked us to document. Pure additive — no existing content modified, 91 insertions / 0 deletions.What's in the new section
.github/workflows/pr-body-refs-lint.yml.os.environoverecho "$VAR"; the command-substitution hazard inside double-quoted shell strings.pull_request(default-safe) vspull_request_target(privileged, fork-unsafe) vsworkflow_dispatch(escape hatch).paths:+ branch-protection interaction (bicameral-daemon#37 / Add workflow_dispatch trigger to test-schema-persistence.yml #123), and theworkflow_dispatch:mitigation.pr-body-refs-lint.yml,lint_pr_body_refs.py, Add workflow_dispatch trigger to test-schema-persistence.yml #123, and label-merged-to-dev workflow fails with 'Resource not accessible by integration' on some PRs #115 so the section stays an index rather than duplicating per-workflow detail.Acceptance check
.github/workflows/pr-body-refs-lint.ymlrather than restating it../.github/...fromdocs/DEV_CYCLE.md)Backward compatibility
Risk
L1 — additive documentation.