re: How-to manage different project release versions in Git? VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Hi, Jonathan. Many thanks for replying. Option 1 seems more like how I envisaged things working, so I'm going to have a play about with things and...
 

Git is super flexible in how you can use it to solve problems. Keeping separate branches gives you the functionality of a fork, but the flexibility of having it in the same repo. Other members of the team and easily check out those different versions and you can merge branches together as you need code to sync up. You can cherry-pick commits if you want some, but not all changes.

One of the biggest challenges ANY project has to overcome is communication. We can have great tools like Git that help us track our changes and share code, but they are useless without good communication.

Especially with the idea you're working with, there's potential for merge conflicts if there isn't enough cross-collaboration between you and the other developers.

code of conduct - report abuse