Skip to content

ci: migrate .github callers to v3.7.1 (App credentials, gitleaks fix) - #197

Merged
DevSecNinja merged 1 commit into
mainfrom
steward/automation-app-callers
Nov 16, 2026
Merged

DevSecNinja merged 1 commit into
mainfrom
steward/automation-app-callers

Conversation

@DevSecNinja

@DevSecNinja DevSecNinja commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

Closes #196

Changes

  • .github/workflows/config-sync.yml: pin config-sync.yml v1.9.0 → v3.7.1 (e28a49a14d4530962b165e0d35a8a331b2b42f23) and pass AUTOMATION_APP_PRIVATE_KEY by 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_KEY yet. Until the owner installs the DevSecNinja Automation App here and provisions them, config-sync falls back to GITHUB_TOKEN with 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: write and pull-requests: write cover v3.7.1; nothing is added. On public repositories the credentials live in the production environment (pinned to main); the reusable job declares it with deployment: false.

Post-merge check

  • Dispatch Config Sync on main: green with no "falls back to GITHUB_TOKEN" warning; the sync PR (by the App) carries the fixed .gitleaks.toml.
  • Record the gitleaks result on that sync PR. New findings are triaged separately, not silenced here.

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

  • Chores
    • Updated the configuration used by repository automation to align with a newer shared workflow revision and use repository-managed authentication. Existing workflow permissions remain unchanged. This internal maintenance update does not change application functionality or the product experience, and it adds no user-facing features.

Part of DevSecNinja/repo-steward#73 (batch 3, the gitleaks wave).

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The config-sync job now uses the DevSecNinja/.github reusable workflow at v3.7.1 and passes AUTOMATION_APP_PRIVATE_KEY from repository secrets. The contents: write and pull-requests: write permissions remain unchanged.

Changes: Config sync workflow

Layer / File(s) Summary
Reusable workflow and credentials
.github/workflows/config-sync.yml
The sync job references v3.7.1 and maps AUTOMATION_APP_PRIVATE_KEY from repository secrets. Both write permissions remain unchanged.

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Other · Severity of issue fixed: Medium

Possibly related issues

  • DevSecNinja/devsecninja-com#2 tracks an update to the same workflow reference that this change updates.
Merge Risk: Minimal · up to b74e6

This updates the config-sync workflow to v3.7.1 and passes the App private key by name. Until the App credentials are provisioned, it falls back to GITHUB_TOKEN with a warning. The change is low risk and safe to merge.

Pre-merge checks: Passed 4

Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title names the main change: the ci workflow caller moves to DevSecNinja/.github v3.7.1, and the title also names the App credentials and gitleaks fix. The raw summary and objectives both describe…
Linked Issues check Passed Issue #196 requires two coding changes in the .github caller: (1) bump .github/workflows/config-sync.yml from v1.9.0 to v3.7.1, and (2) pass AUTOMATION_APP_PRIVATE_KEY by name. The reviewed head…
Out of Scope Changes check Passed The supplied whole-PR summary and PR description identify one changed file, .github/workflows/config-sync.yml (+3/-1), with no permission changes. That file is the file named in #196. No other chang…
Full details: Title check

Explanation

The title names the main change: the ci workflow caller moves to DevSecNinja/.github v3.7.1, and the title also names the App credentials and gitleaks fix. The raw summary and objectives both describe a version bump of config-sync.yml to v3.7.1 that passes AUTOMATION_APP_PRIVATE_KEY, which matches the title. The title is specific and uses the ci: prefix, and it does not describe anything missing from the change.

Full details: Linked Issues check

Explanation

Issue #196 requires two coding changes in the .github caller: (1) bump .github/workflows/config-sync.yml from v1.9.0 to v3.7.1, and (2) pass AUTOMATION_APP_PRIVATE_KEY by name. The reviewed head file uses DevSecNinja/.github/.github/workflows/config-sync.yml@e28a49a14d4530962b165e0d35a8a331b2b42f23 # v3.7.1 and sets secrets: AUTOMATION_APP_PRIVATE_KEY: ${{ secrets.AUTOMATION_APP_PRIVATE_KEY }}. Both requirements are met. The .gitleaks.toml fix ([extend] useDefault = true) is delivered by the config-sync run, as #196 states, so this PR does not need to change .gitleaks.toml. The post-merge checklist items are operational, not coding requirements, and are not assessed. Limitation: the whole-PR text diff was unavailable, so the result relies on the head file read and the supplied summary. The v3.7.1 permission claim lies in an external repository and was not verified; #196 does not state a permission requirement.

Full details: Out of Scope Changes check

Explanation

The supplied whole-PR summary and PR description identify one changed file, .github/workflows/config-sync.yml (+3/-1), with no permission changes. That file is the file named in #196. No other changes are reported. Limitation: the whole-PR text diff and base file listing could not be read, so the file-scope conclusion rests on the supplied summary and the head file contents, not on a full diff comparison against the merge base.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

Share

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 7d7a4e0b-3368-428f-b512-dcc1bc8a6fc5
Commits

Reviewing files that changed from the base of the PR and between 4b20d84 and b74e6a4.

Files selected for processing: 1

  • .github/workflows/config-sync.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟢 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_KEY explicitly while preserving existing permissions.
  • Retains the shared workflow’s GITHUB_TOKEN fallback 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

@DevSecNinja
DevSecNinja merged commit 3d2ed3d into main Nov 16, 2026
13 checks passed
@DevSecNinja
DevSecNinja deleted the steward/automation-app-callers branch November 16, 2026 11:38
@coderabbitai coderabbitai Bot mentioned this pull request Nov 18, 2026
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ci: migrate .github callers to v3.7.1 for the App credentials and the gitleaks fix

2 participants