Skip to content

feat: config sync nested codeowners#146

Merged
DevSecNinja merged 2 commits into
mainfrom
feat/config-sync-nested-codeowners
Jun 1, 2026
Merged

feat: config sync nested codeowners#146
DevSecNinja merged 2 commits into
mainfrom
feat/config-sync-nested-codeowners

Conversation

@DevSecNinja
Copy link
Copy Markdown
Owner

Description

Changes

Checklist

  • Linting passes locally (mise exec -- lefthook run pre-commit)
  • Commit messages follow Conventional Commits
  • Documentation updated (if applicable)

Copilot AI added 2 commits June 1, 2026 13:57
…t-out

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…st-credentials

Preempt the same GHAS findings reported on PR #84:

- zizmor: credential persistence through GitHub Actions artifacts.
  Both checkouts now set `persist-credentials: false`. The
  `actions/open-pr` composite action authenticates via its own
  `github-token` input (defaulting to `${{ github.token }}`), so
  no persisted creds are required for the PR creation step.

- Checkov: ensure top-level permissions are not set to write-all.
  Top-level `permissions` is now `contents: read` (least
  privilege); the elevated `contents: write` and
  `pull-requests: write` are scoped to the `sync` job only —
  matching the pattern already used by `release-please.yml`.

Verified: `zizmor` reports no findings; `actionlint` (incl.
shellcheck) clean; `yamlfmt` clean against the central config.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@DevSecNinja DevSecNinja force-pushed the feat/config-sync-nested-codeowners branch from f5bfc90 to 8448d26 Compare June 1, 2026 11:58
@DevSecNinja DevSecNinja changed the title Feat/config sync nested codeowners feat: config sync nested codeowners Jun 1, 2026
@DevSecNinja DevSecNinja merged commit f296be4 into main Jun 1, 2026
16 checks passed
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