managing-github-actions-secrets

What problem does it solve?

Teams often add GitHub Actions secrets at the wrong scope, exposing credentials to too many repositories or scattering secrets across individual repos. This Skill enforces PostHog's policy of centralizing all CI secrets at the organization level with controlled per-repository access.

Core Features & Use Cases

• Org-level secret creation: Guides creating secrets on the posthog org via gh secret set --org posthog or the GitHub UI, never at the repo level.
• Scoped repository access: Shows how to grant secrets to selected repositories using --visibility selected --repos instead of exposing them org-wide.
• Safe secret handling: Enforces piping values from stdin or files so secrets never appear in shell history, chat, commits, or logs.
• Use Case: When wiring a new workflow to a package registry credential referenced as ${{ secrets.POSTHOGOS_PACKAGER_KEY }}, use this Skill to create the secret at the org level and grant access only to the repos that need it.

Quick Start

Ask the assistant to create a new GitHub Actions secret for a PostHog workflow and grant it access to the specific repositories that need it.