Repository navigation
ci: migrate .github callers to v3.7.1 (App credentials, gitleaks fix) - #197
Conversation
Part of DevSecNinja/repo-steward#73 (batch 3, the gitleaks wave). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues were identified for the Config Sync caller’s GitHub App authentication update.
No open issues 🎉
What changed in this PR
Updates the repository’s shared Config Sync caller to support GitHub App authentication, enabling future sync PRs to trigger CI and deliver the central gitleaks configuration fix once App credentials are provisioned.
Changes:
- Bumps the pinned reusable workflow from v1.9.0 to v3.7.1.
- Passes
AUTOMATION_APP_PRIVATE_KEYexplicitly while preserving existing permissions. - Retains the shared workflow’s
GITHUB_TOKENfallback until App credentials are available.
| File | Description |
|---|---|
.github/workflows/config-sync.yml |
Updates the shared workflow pin and forwards the App private-key secret. |
Review effort: Balanced
Closes #196
Changes
.github/workflows/config-sync.yml: pinconfig-sync.ymlv1.9.0 → v3.7.1 (e28a49a14d4530962b165e0d35a8a331b2b42f23) and passAUTOMATION_APP_PRIVATE_KEYby name, so the sync PR is opened by the DevSecNinja Automation App (App-opened PRs run CI). The next sync delivers the fixed.gitleaks.toml([extend] useDefault = true, so gitleaks keeps its default rules and only adds the allowlist).This repository has no
AUTOMATION_APP_ID/AUTOMATION_APP_PRIVATE_KEYyet. Until the owner installs the DevSecNinja Automation App here and provisions them, config-sync falls back toGITHUB_TOKENwith a warning, as it effectively does today. The fixed gitleaks config arrives with the first App-authenticated sync after that. Renovate #134 only bumps this caller and is superseded.Permissions:
contents: writeandpull-requests: writecover v3.7.1; nothing is added. On public repositories the credentials live in theproductionenvironment (pinned tomain); the reusable job declares it withdeployment: false.Post-merge check
main: green with no "falls back to GITHUB_TOKEN" warning; the sync PR (by the App) carries the fixed.gitleaks.toml.Part of DevSecNinja/repo-steward#73 (batch 3, owner-approved). Opened by repo-steward through the GitHub API; the commit is signed by GitHub (
createCommitOnBranch).Summary by CodeRabbit