After reviewing a feature branch, a team decides not to merge it into the main branch. What Git strategy can be used to preserve the work done on this feature branch for future reference?
- Reset
- Revert
- Archive
- Branch
Creating a new branch allows the team to preserve the work done in the feature branch without merging it into the main branch, keeping the changes isolated for future reference.
Loading...
Related Quiz
- In the context of Git, what is a 'sparse checkout' and how does it improve performance with large repositories?
- How can you create an annotated tag in Git that includes a message?
- How does Git's branching model enhance Agile methodologies in large-scale development?
- Which command in Git allows you to view the commit history?
- What is the purpose of the .gitignore file in a Git repository?