Git - Collaboration Workflows
In a workflow enforcing pull requests for main branch changes, what happens if a developer pushes directly to main?
In a workflow enforcing pull requests for main branch changes, what happens if a developer pushes directly to main?
medium📝 Predict Output Q5 of 15
Step-by-Step Solution
Solution:
Step 1: Understand branch protection
Branch protection rules prevent direct pushes to main to enforce reviews.Step 2: Analyze options
Only The push is rejected due to branch protection rules correctly describes rejection of direct push; others are incorrect behaviors.Final Answer:
The push is rejected due to branch protection rules -> Option DQuick Check:
Branch protection blocks direct pushes [OK]
Quick Trick: Protected branches reject direct pushes [OK]
Common Mistakes:
- Assuming push bypasses review
- Believing Git auto-creates pull requests
- Thinking local branches get deleted automatically
Master "Collaboration Workflows" in Git
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Git Quizzes