docs(workflows): document Bumblebee Supply-Chain Scan#45
Conversation
Add a section to docs/workflows.md mirroring the existing per-workflow entries (publish-techdocs, release-auto-on-tag, cdk-deploy-monitor). Covers the trigger model, inputs, outputs on a finding, and the one-click "New workflow" enablement path. Pairs with the consumer-side ops documentation in geolonia-operations.
Secret Leak CheckOK No secrets detected in this PR's diff. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThis PR adds documentation for the Bumblebee Supply-Chain Scan reusable workflow, describing triggers, delegated actions (download/pinned Bumblebee and threat-intel matching), PR vs non-PR reporting, inputs/outputs, minimal usage, and steps to add/configure the workflow. ChangesBumblebee Supply-Chain Scan Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/workflows.md`:
- Around line 115-118: The docs currently claim the workflow runs on "schedule /
workflow_dispatch / release / push" which is inaccurate for the reusable
`workflow_call`-only template; update the paragraph that mentions `schedule`,
`workflow_dispatch`, `release` and `push` to reflect the actual triggers used by
the template (it supports `workflow_call` and the default template enables
`pull_request`, `schedule` (cron) and `workflow_dispatch`), removing or
clarifying `release` and `push` (or explicitly state that `release`/`push` only
apply when invoked by non-template callers) so the text matches the workflow
configuration.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: b85670f5-be74-490b-a9c7-232532529490
📒 Files selected for processing (1)
docs/workflows.md
The reusable workflow is workflow_call-only; the default template enables pull_request + schedule + workflow_dispatch (release commented, push not configured). Reword the issue-on-finding bullet to say 'any non-PR trigger' and note which the template enables vs. what callers may add, instead of listing release/push as if active.
Secret Leak CheckOK No secrets detected in this PR's diff. |
Summary
Documents the Bumblebee reusable workflow + template under
docs/workflows.md, matching the existing per-workflow sections.Why
The reusable workflow + template were added in #44 /
v1.14.0, but the documentation was never updated. New adopters land ondocs/workflows.mdand currently do not see Bumblebee listed.What was added
A
## Bumblebee Supply-Chain Scansection betweenRelease on TagandUpdating templates, covering:No code changes.
Test plan
Summary by CodeRabbit