cancel
Showing results for 
Search instead for 
Did you mean: 

Documentation for Multiple Developers Working in the Same Git Project

fxs7576
9 - Travel Pro
9 - Travel Pro

I have a Git enabled project (say named 'Project A') in which it's always connected to 'main' branch. Knowing the current constraints:

  • A project can only have one active branch.
  • Each asset can only be assigned to one project.
  • Each asset can only have one owner/user.

Is there documentation or a tutorial as a guide for how multiple developers can perform these actions?

  • Multiple developers can modify the same existing assets in 'Project A' simultaneously. Is the solution specified here still the only way?
  • Proposal to merge:
    • Developer 01 creates a feature branch to edit the existing asset;
    • Developer 01 creates a pull request;
    • Developer 02 reviews the change;
    • Developer 01 merges the feature branch to 'main' branch.

Thanks

 

1 ACCEPTED SOLUTION

DRay
Community Team Member
Community Team Member

Hello @fxs7576,

Thank you for your question. Can you take a look at this thread and let me know if it addresses your use-case? 

https://community.sisense.com/t5/deploy-connect-analytics/best-practises-for-co-dev-in-version-contr...

Thank you,

 

David Raynor (DRay)

View solution in original post

2 REPLIES 2

DRay
Community Team Member
Community Team Member

Hello @fxs7576,

Thank you for your question. Can you take a look at this thread and let me know if it addresses your use-case? 

https://community.sisense.com/t5/deploy-connect-analytics/best-practises-for-co-dev-in-version-contr...

Thank you,

 

David Raynor (DRay)

fxs7576
9 - Travel Pro
9 - Travel Pro

Hi @DRay , thanks and yes. The use case mentioned in that thread is similar to mine: It has the same issue, and we might be looking for the same solution.