Best Practices
Copia shines when used in collaboration with multiple engineers. Some of the benefits of using Copia for collaboration include:
- Ability to invite external users or contractors with read-only seats.
- Ease of transferring repositories to clients
- Use of Copia across different Teams and functions as a source of truth for accessing the latest version of a project
To learn more about collaborative features like Organizations, Teams, Issue Tracking, and Wikis, check out the Advanced section.
But generally, there are several rules of thumb to keep in mind when collaborating using Copia:
- Keep branches short-lived.
- Generally, the turnaround time of merging a branch should be quick. This also means that branches should be relatively small.
- Try to have everyone merging into the same branch (Prefer fewer target branches)
- Generally, everyone on your team should be merging into the same branch (the mainline). Releases and release candidates (RCs) should branch off of the mainline.
- Merging between multiple non-mainline branches is discouraged.
Copia supports the use of virtual machines. You can either run the Copia Desktop App app from within the virtual machine or via the host.
We recommend that you create a shared folder between the virtual and host machines. This way, you can run Copia on the host machine and monitor the shared folder from as many VMs/IDEs as needed.
This suggested workflow allows Copia users to make changes on one machine as opposed to switching back and forth between multiple machines.
Last modified 5mo ago