The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Sourcetree plus git best workflow

unity3d-profile-design-pattern
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 22, 2021

We are 4 devs working on a single game, artists and developer combined

The way we are doing it is having, individual branches dev1 , dev2 , dev3 , dev4, and developer branches.

Each dev pushes the changes in his own branch When it's time to integrate what I do is a pull from the respective branch into developer.

Is this workflow accurate to ensure changes from all devs are saved into developer branch,  If not what's the correct workflow for doing this ?

 

Assuming developer is the first branch from main and all 4 branches separated from here

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Teck Hooi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 24, 2021

My suggestion is to have a single develop (developer) branch and have the completed features merged back into the develop branch. Merge quickly back to the develop branch instead of having long-running branches like dev1, dev2, etc. This is to make sure no feature is missed out during testing and you save the time meant for integration. Furthermore, if you leave everything to "integration" to merge all the changes back to the `develop` branch, the changes might be overwhelming to deal with

TAGS
AUG Leaders

Atlassian Community Events