Collaboration best practices and merging

Need help
1

My cofounder and I are working on an app as collaborators. We would like to know more about best practices and experiences for collaboration.

Our app is currently in development and hasn’t been published yet. We currently use two dev versions (more is not possible due to budget restraints). We pull changes from my cofounders dev version (“version b”) into my, the main dev version (“version a”). Due to the lack of a third version, if I create a critical error, the only option would be to revert to a previous point. Our interest lies in particular in:

  • What is a good review process to make sure that we only pull sensible changes?
  • Is it possible to only pull certain changes from version b → version a and not the entire version?
  • What are further tips & tricks for collaboration?

I appreciate any advice! Thank you.

2

Hello @moritzhd

Keep dev free of issues
Only do dev work in the branches
Publish to dev from branches as frequent as possible.
Do not let more than one week of changes not be synched to dev. After change is posted delete the branch and start a new one from the updated dev version .

3

Hi @cmarchan ,
Thank you for your advice.
The main problem is that that only leaves us with one dev version (version b) to work in which is very unpractical.

As mentioned in my post, what you are describing is the setup we would have chosen, if we were on the product plan, but that is an additional 400$/month and currently not affordable.

4

This topic was automatically closed after 70 days. New replies are no longer allowed.