fix(ci): do not persist the job token in .git/config in the public-repo guard

[yakimoto]

Why

actions/checkout without persist-credentials: false writes the job's GITHUB_TOKEN into
.git/config, where any later step — or anything those steps execute — can read it. This is the
security gate that DOWNLOADS AND EXECUTES the gitleaks binary, and the workflow's own comment
already reasons about tampered downloads ("so a tampered or MITM'd download can never execute
inside the security gate"), so the threat model is written down and only the credential half of
the mitigation is missing. Found by zizmor as warning[artipacked]: credential persistence through GitHub Actions artifacts.

Safety

Verified this job only: checks out, installs gitleaks (pinned + checksum), runs
gitleaks detect --no-git, installs ripgrep, runs content-policy.sh. permissions: contents: read. Nothing pushes, calls gh, or reads GITHUB_TOKEN/GH_TOKEN, so the token was never needed
in .git/config in the first place.

Refs wave-av/claude-workstation#1870.

---

Note

Low Risk
Single checkout hardening with no behavior change for scans; reduces credential exposure in a security gate workflow.

Overview
Hardens the public-repo-guard workflow by setting persist-credentials: false on actions/checkout, so the job’s GITHUB_TOKEN is not written into .git/config for later steps.

That matches how other CI workflows in this repo already configure checkout and closes the gap zizmor flagged (artipacked) in a job that downloads and runs the pinned gitleaks binary plus content-policy.sh—steps that could otherwise read persisted credentials even though this gate only needs contents: read and never uses the token for push or gh.

^{Reviewed by Cursor Bugbot for commit 576b52a. Configure here.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 30 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 72842113-6aad-4e0f-a6c2-2f68ee7ad003

📥 Commits

Reviewing files that changed from the base of the PR and between 1abc3a1 and 576b52a.

📒 Files selected for processing (1)

• .github/workflows/public-repo-guard.yml

---

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_4a7b140b-06ca-4928-a419-5b5d0a581bb6)

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[macroscopeapp]

Approvability

Verdict: Approved 576b52a

This is a minor CI security hardening change that adds persist-credentials: false to prevent the job token from being stored in .git/config. The author owns this workflow file. No application runtime impact.

^{You can customize Macroscope's approvability policy. Learn more.}

[qodo-code-review]

PR Summary by Qodo

CI: disable checkout credential persistence in public-repo guard

🐞 Bug fix ⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Prevents actions/checkout from writing GITHUB_TOKEN into .git/config for later steps.
• Hardens the public-repo security gate that downloads and executes pinned tooling.

Diagram

graph TD
  A["public-repo-guard job"] --> B["actions/checkout"] --> C{persist-credentials?
false}
  C -->|"do not write token"| D[(".git/config")]
  B --> E["scan steps (gitleaks/content-policy)"]
  E -. "cannot read token from git config" .-> D

Loading

High-Level Assessment

Setting persist-credentials: false on the checkout step is the standard, lowest-risk mitigation for preventing token persistence in .git/config and is appropriate here given the job doesn’t need git-authenticated operations beyond a read-only checkout.

Files changed (1) +2 / -0

Other (1) +2 / -0

public-repo-guard.ymlDisable credential persistence for the workflow checkout +2/-0

Disable credential persistence for the workflow checkout

• Adds 'persist-credentials: false' to the 'actions/checkout' step so the job token is not stored in '.git/config' and is therefore not accessible to later steps in this security gate workflow.

.github/workflows/public-repo-guard.yml

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}

[qodo-code-review]

Qodo Fixer

No findings are available for this PR yet. Findings appear here once Qodo has reviewed the PR.

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[yakimoto]

This PR is redundant with #338 (chore/guard-canonical-sync), which is already open and already contains this exact change.

Evidence — #338's diff to .github/workflows/public-repo-guard.yml includes:

+          # tree. Nothing here pushes -- the scan is `--no-git` over the working tree --
+          # so no step needs authenticated Git; drop it. (zizmor: artipacked)
+          persist-credentials: false

#338 is also broader than this PR: it syncs the whole vendored public-repo-guard trio to
the canonical source (wave-foundation/scaffolder/public-repo-guard) byte-for-byte, verified by
git blob SHA, rather than adding this one line in isolation.

Closing as redundant. This duplicate exists because the fan-out that opened this PR
(refs claude-workstation#1870) did not check for in-flight PRs touching the same file before
going out — #338 was already open. Merge #338 instead.