(Unofficial) Anvil Version Control for Dummies

[AWSOM]

@david.wylie

What I would like to see is a really, really clear set of instructions, with pictures, of a team project set up where, for example, 2 people are working on the UI and 2 people are working on the back end. Advice on how to ensure no one clashes, what to do if they do, how to merge all the code, best practises. A proper guide that idiots like me could stick up on my wall and use as a bible, from someone(s [sic]) who really, really understand the process.

I’d like to see that too but certainly don’t “really really understand the process”!

I think the foundations of an answer will be obvious if my Feature Request is actioned, at which point you could simply create new branches “Dev1 - Back End”, “Dev2 - Back End”, “Dev3 - UI”, and “Dev4 - UI” in Github after inviting collaborators to the master Anvil remote. Each developer would create their own branch and when ready create a pull request for the app owner to review, discuss, and decide whether to merge using organic Github functionality.