Changing the history of public branches is generally discouraged because it can lead to ________ for other collaborators.
- synchronization issues
- confusion
- conflict resolution
- frustration
The correct option is (c) conflict resolution. Altering the history of public branches can create conflicts for other collaborators, making it challenging to resolve differences in the repository. It's a good practice to avoid history changes on shared branches.
Loading...
Related Quiz
- A development team is implementing a code quality tool into their Git workflow. They need to automatically reject commits that don't meet the quality standards. Which Git feature should they leverage?
- GitLab’s CI/CD pipelines can be configured through a file named _________.
- In secure Git practices, a _______ branch strategy involves using separate branches for development and production.
- The __________ feature in Bitbucket is used for integrating with third-party services.
- In resolving conflicts, the _______ command can be used to revert files to their state before the merge conflict.