After reviewing a repository's history, a team leader finds an unauthorized access. What Git practice could have prevented this?
- Branch protection
- Code signing
- Git hooks
- Commit squashing
Branch protection can prevent unauthorized access by defining rules that restrict certain actions on specific branches. By enforcing access controls, the team leader could have prevented unauthorized changes and maintained a secure repository.
Loading...
Related Quiz
- A developer needs to integrate their feature branch with the latest updates from the main branch, but wants to maintain a clean history. Should they use merge or rebase, and why?
- What is the main difference between git fetch and git pull?
- What is the purpose of a .gitignore file in a Git repository?
- To maintain a clean Git history when transitioning, it's recommended to use git ________ for combining multiple commits.
- In Git, the __________ file can be used to enforce code quality standards across all project contributors.