A company uses Git for both application code and database version control. How should they structure their repositories to manage changes effectively?
- Single Repository with Multiple Folders for Code and Database
- Separate Repositories for Code and Database
- Git Submodules
- Git Subtrees
The company should use Separate Repositories for Code and Database. This approach provides clear separation between application code and database version control. Each repository can have its own history, branches, and releases, making it easier to manage changes independently. It also helps in maintaining a clean and focused history for each component, facilitating collaboration and version control for both application code and the database.
Loading...
Related Quiz
- In the context of large-scale collaborative projects, what is a key advantage of using the Forking workflow over Gitflow?
- In large projects, Git's __________ feature is crucial for managing different development streams.
- After performing a rebase, you may need to use git ______ to incorporate the changes into the base branch.
- When a merge conflict occurs, what does Git use to mark the conflicted area in the files?
- GitLab’s CI/CD pipelines can be configured through a file named _________.