GH-100 GitHub Administration Questions and Answers

You declare named inputs in the reusable workflow’s on.workflow_call block and then pass values from the caller using the with keyword, allowing the called workflow to consume those parameters.

You define required secrets in the caller repository and supply them to the reusable workflow via the secrets keyword in the workflow-call step, ensuring sensitive values are securely passed.

Group SCIM lets you manage both user accounts and group memberships centrally in your identity provider - automatically provisioning, updating, and deprovisioning users and groups in GitHub - whereas Team Sync only mirrors IdP group membership into existing GitHub teams.

Revoke and/or rotate the exposed credentials immediately so they can no longer be used - this is the critical first step before you undertake any history‑rewriting or cleanup.

GitHub Premium Support includes assistance with installing and using GitHub Enterprise Server, ensuring your deployment is configured correctly and any installation issues are resolved.

GitHub Actions billing for GitHub‑hosted runners is based on the number of minutes consumed and the operating system of the runner - Linux, Windows, and macOS each have different per‑minute rates.

GitHub Actions workflows are defined and triggered within a single repository’s context, whereas GitHub Apps are installed at the organization or user level and can subscribe to events across multiple repositories.

GitHub Apps authenticate with short‑lived installation tokens scoped to fine‑grained permissions and, when owned by a GitHub Enterprise Cloud organization, enjoy a higher rate limit (15,000 requests/hour) compared to a machine account’s personal access token.

GitHub Discussions engagement isn’t a metered product and doesn’t appear in the “Product billing” list, so its usage isn’t included in the monthly metered billing report.

EMU accounts are provisioned and authenticated exclusively through your identity provider - users sign in via the IdP and cannot use or manage GitHub-native credentials.

The Dependency Graph continuously analyzes your repository’s manifest and lock files to build an inventory of direct and transitive dependencies and flags any that match entries in the GitHub Advisory Database, surfacing known vulnerabilities.

SCIM automatically updates a user’s account on GitHub whenever their profile attributes change in the identity provider.

When a user is removed or deactivated in the IdP, SCIM deactivates (soft‑deprovisions) their GitHub account and disables access.

SCIM provisions new GitHub Enterprise Cloud accounts automatically when users are added in the identity provider.

The GraphQL Audit Log API surfaces entries whenever repository or organization permissions are changed (“Changes permissions”).

It records when users are elevated to administrative roles (“Promotes users to admin”).

It logs alterations to a GitHub App’s granted permissions (“Changes permissions of a GitHub App”).

Regularly auditing for inactive (dormant) users lets you suspend or remove accounts that aren’t consuming seats - freeing up licenses and directly lowering your per‑user subscription costs.

Organization owners can view and edit billing information for the organization.

Organization owners may create new repositories in the organization without needing approval from other members.

Organization owners have full administrative control over organization settings, including configuring default repository permissions.

Team maintainers can manage nested sub‑teams - requesting to add or change parent/child teams within the organization’s hierarchy.

Team maintainers have permission to add and remove members from their team, controlling day‑to‑day team membership.

Before you enable team synchronization, you should clearly define how groups in your identity provider will map to GitHub teams and roles - ensuring that when the sync runs, users land in the correct teams with the right permissions.