This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Why do enterprises commonly restrict direct pushes to the default branch?
To reduce repository size.
To enforce review, testing, and auditability.
To limit developer access.
Because GHES does not support direct pushes.
What is the primary purpose of branch protection rules?
Improve UI performance.
Enforce collaboration and governance policies.
Automatically resolve merge conflicts.
Replace pull requests.
Why are pull requests especially important in GHES environments?
They reduce storage usage.
They enable GitHub Actions.
They provide collaboration, control, and traceability.
They eliminate the need for documentation.
Your pull request has an approval, but the merge option is disabled because a required status check is failing. What should you do first?
Push directly to the protected branch to bypass the pull request.
Ask a teammate to merge it without fixing the check.
Investigate and fix the failing check, then re-run validation.
Delete and recreate the branch.
A pull request modifies a directory that requires review from code owners, but no code owner has approved it. What is the most likely next step?
Merge anyway because at least one reviewer approved.
Request review from the required code owners and wait for approval.
Convert the pull request to a draft and merge immediately.
Delete the branch protection rule.
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?