GitHub Administration case studies
GitHub Administration · Put your knowledge to work in context.
This independent study page provides practice for GitHub Administration. Its editorial learning areas include GitHub enterprise administration, identity and repository controls; GitHub Actions policy, runner trust and workflow administration; Identity, access and cryptographic protection; Security operations, monitoring and response; Continuity, backup and technical recovery. The GitHub Administration case studies are 5 cases and about 992 words.
1A code-owner file without an enforcing review rule
A fictional repository has a CODEOWNERS file that maps an infrastructure directory to an eligible team. A supplied test pull request requests that team’s review, but its protected branch has no required code-owner approval setting.
163 words, under 1 min2A runner group permits execution but does not isolate code
A fictional organization limits a self-hosted runner group to two repositories. A proposed workflow from one allowed repository can still execute code from an untrusted contribution, and the host retains sensitive network reachability and state between jobs.
166 words, under 1 min3SaaS access after a role change
A fictional organization uses a managed collaboration service for internal planning documents. The provider maintains the application and underlying servers, while the organization configures users, groups and sharing settings.
221 words, about 1 min4An incident review with an action that can be checked
A fictional delivery team restores service after a release encounters an undocumented database dependency. The initial meeting ends with the statement that the engineer should be more careful, but no owner, test or review date is recorded.
219 words, about 1 min5A recovery target does not prescribe one universal architecture
A fictional order service has a recovery-point objective of fifteen minutes and a recovery-time objective of four hours. A tested option creates consistent recovery points every ten minutes and restores the service in three hours after the declared recovery procedure begins.
223 words, about 1 min