Enforcing One Issue Template Across an Entire GitHub Organization
Your organization uses GitHub Enterprise and wants to enforce that all repositories have a specific issue template. What is the most scalable way to achieve this?
Quick Answer
Creating a global issue template by placing it in the organization's special .github repository is the scalable path — GitHub automatically applies it across every repository in the organization, so there's no need to manually copy the template into each repo individually or maintain per-repo consistency by hand.
⚠ Common exam trap
A common mix-up: candidates confuse repository templates (which only affect new repos) with organization-level templates (which apply globally), leading them to choose option C as a scalable solution.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a global issue template in the organization settings.
GitHub Enterprise allows organization owners to create a global issue template by placing a `.github/ISSUE_TEMPLATE/` directory in the `.github` repository. This template is automatically applied to all repositories within the organization, ensuring consistency without manual intervention per repo. This is the most scalable approach as it centralizes enforcement at the organization level.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a global issue template in the organization settings.
Why this is correct
Global templates apply to all repositories.
- ✗
Use a script to periodically check and add templates.
Why it's wrong here
Not enforced and not scalable.
- ✗
Create a repository template and require all new repos to use it.
Why it's wrong here
Does not affect existing repositories.
- ✗
Configure a CODEOWNERS file in each repository.
Why it's wrong here
CODEOWNERS is for code review, not templates.
Go deeper
Related to this question
Learn chapter
Final Review and Exam Preparation
Key term
Repository
A repository is a central storage location where software packages, code, or configuration files are kept, managed, and distributed for use by IT systems.
Key term
GitHub
GitHub is a cloud-based platform for storing, tracking, and collaborating on code using Git version control.
About these practice questions
Courseiva writes every AZ-400 question from scratch — 823 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on AZ-400
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Your team uses GitHub Issues to track work. You want to enforce that all new issues include a specific set of labels based on the issue type (bug, feature, task). What is the most efficient way to achieve this?
medium- A.Configure branch protection rules to require label assignments.
- B.Use a CODEOWNERS file to auto-assign labels.
- ✓ C.Create YAML-based issue forms in the .github/ISSUE_TEMPLATE folder.
- D.Set up a repository ruleset to restrict label modifications.
Why C: GitHub issue forms, defined as YAML files in the .github/ISSUE_TEMPLATE folder, allow you to create structured templates that can enforce required fields, including mandatory label assignments. When a user submits an issue via a form, the labels specified in the template are automatically applied, ensuring consistency without manual intervention or additional automation.
Variation 2. Your organization uses GitHub Enterprise and wants to enforce that all repositories have a consistent CODEOWNERS file. Which approach should you use to centrally manage this?
hard- A.Use repository rulesets to require that the CODEOWNERS file exists and has a specified pattern
- ✓ B.Create a CODEOWNERS file at the organization level
- C.Use a script to push CODEOWNERS to each repo manually
- D.Create a GitHub Actions workflow that runs on push to check CODEOWNERS
Why B: In GitHub Enterprise, you can create a special repository named `.github` at the organization level. A CODEOWNERS file stored in that repository is applied as a default to all repositories in the organization, providing centralized management. Repository rulesets cannot require that a file exists; they enforce branch/tag rules such as required reviews and status checks, but not file existence.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.