Skip to content

docs(code-review): pin examples to @main and drop unused security inputs#1039

Merged
factory-nizar merged 2 commits into
mainfrom
docs/code-review-pin-main
Apr 28, 2026
Merged

docs(code-review): pin examples to @main and drop unused security inputs#1039
factory-nizar merged 2 commits into
mainfrom
docs/code-review-pin-main

Conversation

@factory-nizar
Copy link
Copy Markdown
Contributor

@factory-nizar factory-nizar commented Apr 28, 2026

Summary

Companion docs update to Factory-AI/droid-action#80. Cleans up the code-review and security-review docs to match what the action actually does today, and sweeps the rest of the docs for stale Factory-AI/droid-action@vN references.

Changes

Pinning to @main (matches the workflow that /install-code-review generates):

  • docs/guides/droid-exec/code-review.mdxFactory-AI/droid-action@v3@main in the scheduled-scan example.
  • docs/jp/guides/droid-exec/code-review.mdx — same.
  • docs/integrations/github-app.mdx@v3@main in the install-via-CLI workflow snippet.
  • docs/jp/integrations/github-app.mdx — same.
  • docs/enterprise/github-integration-security.mdx@v1@main in the network-restrictions example.
  • docs/jp/enterprise/github-integration-security.mdx — same.

After this PR, rg 'droid-action@v[0-9]' docs/ returns zero matches.

Drop misleading config: security_block_on_critical, security_block_on_high, and security_notify_team are declared in action.yml and parsed into context, but nothing in droid-action's prompt or review-submission code currently reads them — so they're effectively no-ops today. Documenting them as functional is misleading. Removed from:

  • docs/guides/droid-exec/code-review.mdx — "Security configuration" and "All workflow inputs" tables.
  • docs/jp/guides/droid-exec/code-review.mdx — same tables (Japanese).

Drop "PR blocking on critical findings" claim from the code-review feature overview, for the same reason:

  • docs/cli/features/code-review.mdx
  • docs/jp/cli/features/code-review.mdx

security_severity_threshold is kept everywhere because it is wired up — it's injected into the security scan prompt as the filter threshold.

Validation

  • rg 'security_block_on_critical|security_block_on_high|security_notify_team' docs/ → no matches in the touched pages.
  • rg 'droid-action@v[0-9]' docs/ → no matches anywhere under docs/.

- Update Factory-AI/droid-action workflow examples from @V3 to @main, matching
  what the /install-code-review installer generates.
- Remove security_block_on_critical, security_block_on_high, and
  security_notify_team from the security configuration and workflow inputs
  tables. These inputs are declared in action.yml but not currently consumed
  by the action's logic, so documenting them as functional is misleading.
- Drop the 'PR blocking on critical findings' bullet from the cli/features
  code-review overview for the same reason.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented Apr 28, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
factory 🟢 Ready View Preview Apr 28, 2026, 6:02 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@factory-droid
Copy link
Copy Markdown
Contributor

factory-droid Bot commented Apr 28, 2026

Droid finished @factory-nizar's task —— View job


Docs changes look consistent and remove misleading/no-op security inputs; the main remaining suggestion is to add a brief security note near the droid-action@main example clarifying the pinning tradeoff.

Sweeps the github-app integration page and the github-integration-security
enterprise page (EN + JP) to use Factory-AI/droid-action@main, matching the
ref the /install-code-review installer generates.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
runs-on: ubuntu-latest
steps:
- uses: Factory-AI/droid-action@v3
- uses: Factory-AI/droid-action@main
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P2] [security] Add a pinning note for droid-action@main

The example now uses a mutable ref (@main), which is easy to copy/paste but also a supply-chain footgun in GitHub Actions. Consider adding a short inline note in the snippet to encourage pinning to an immutable ref (commit SHA/release) or to make the tradeoff explicit.

Suggested change
- uses: Factory-AI/droid-action@main
- uses: Factory-AI/droid-action@main # Security note: consider pinning to a commit SHA for immutable, auditable builds.

Comment thread docs/jp/guides/droid-exec/code-review.mdx
Copy link
Copy Markdown
Contributor

@TheFactoriousDROID TheFactoriousDROID left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good thanks. I'll fix the JP sync workflow so it comments in english

@factory-nizar factory-nizar merged commit 554d0e3 into main Apr 28, 2026
7 checks passed
@factory-nizar factory-nizar deleted the docs/code-review-pin-main branch April 28, 2026 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants