Skip to content

Add CODEOWNERS requiring Splunk Dev review - #6

Merged
pbujna-apius merged 1 commit into
mainfrom
chore/add-codeowners
Jul 20, 2026
Merged

Add CODEOWNERS requiring Splunk Dev review#6
pbujna-apius merged 1 commit into
mainfrom
chore/add-codeowners

Conversation

@pbujna-apius

Copy link
Copy Markdown
Contributor

Assigns the @apius-tech/splunk-dev team as code owner for all paths so every PR must be approved by a Splunk Dev member before merge. Part of public-repo hardening (splunk-app-standards#12).

@pbujna-apius
pbujna-apius merged commit d77214e into main Jul 20, 2026
1 check passed
pbujna-apius added a commit that referenced this pull request Jul 20, 2026
Wires this app into the gated Splunkbase publish added in slice #6 (ADR-0006):
- Forward splunkbase_app_id: ${{ vars.SPLUNKBASE_APP_ID }} to the reusable
  release workflow. The SPLUNKBASE_APP_ID repo variable is already provisioned
  (=9192); if it were unset the reusable workflow would skip the publish.
- Keep `secrets: inherit` so SPLUNK_USER/SPLUNK_PASS reach the publish job;
  they are scoped to the `splunkbase` Environment, whose required reviewer is
  the manual approval gate.

No behaviour change to packaging, AppInspect, or the GitHub Release.
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.

1 participant