git-ape-onboarding

OIDC federated credentials are configured by creating an Entra app registration and establishing trust between Azure AD and GitHub Actions. This skill automates that federated identity setup to enable passwordless authentication for repository deployments.

Multi-environment Azure deployments require GitHub environments like azure-deploy* and azure-destroy, plus secrets including AZURE_CLIENT_ID, AZURE_TENANT_ID, and AZURE_SUBSCRIPTION_ID. This skill provisions them automatically during the onboarding workflow.

Yes, repository onboarding for Azure deployments can be automated without manual RBAC configuration. This skill assigns required roles across subscriptions and creates environment guardrails interactively by gathering your repository and subscription context.

The best way to bootstrap a new Azure subscription for Git-Ape deployments is through an interactive onboarding workflow. This skill guides you through Entra app registration, OIDC credentials, RBAC roles, and GitHub environment provisioning in a repeatable process.

No, existing GitHub environments are not required before onboarding. This skill creates the necessary environments, such as azure-deploy* and azure-destroy, and stores the required deployment secrets as part of the automated setup process.

Federated credentials are needed to establish OIDC trust between GitHub Actions and Azure Entra ID, removing the need for long-lived secrets. This skill configures the federated identity to ensure smooth, secure authentication for Git-Ape deployments.