Sympli

If you're using <a href="https://help.sympli.io/en/articles/3859496-how-to-create-and-use-branches">branches</a> in Sympli Versions to manage your workflow and save up production time, here is a list of tips on how to get the most out of this awesome part of version control.

It is important that you choose the way your team is going to approach what goes into the branch. We've seen teams working with Design Sprints that are incorporated in the release cycles - they are using branches to work on the features and use one branch for one feature. We've also seen teams that use branches as a personal work file, that each designer on the team has, and before he can contribute to the main design file, his work goes through the Design Review. It's helpful to pick a workflow and stick to it.

Writing clear commit messages helps every collaborator a lot of time on the communication of what was done. It also makes the history of changes meaningful for anyone that will work on the project later. And if something went wrong, you can find the version of the file where it happened faster.

Committing regularly and not stashing changes is one of the great things to do too. Remember, we're trying to get rid of losing track of what was done and when. Also, if your commit has too many changes, you'll lose all of them, if you need to roll back to the previous version.

Make a habit of updating your branch with the changes from the Main branch frequently. This will allow you to have fewer conflicts when merging and you'll always see the latest version of the main design.

1. It is important that you choose the way your team is going to approach what goes into the branch. We've seen teams working with Design Sprints that are incorporated in the release cycles - they are using branches to work on the features and use one branch for one feature. We've also seen teams that use branches as a personal work file, that each designer on the team has, and before he can contribute to the main design file, his work goes through the Design Review. It's helpful to pick a workflow and stick to it.
2. Writing clear commit messages helps every collaborator a lot of time on the communication of what was done. It also makes the history of changes meaningful for anyone that will work on the project later. And if something went wrong, you can find the version of the file where it happened faster.
3. Committing regularly and not stashing changes is one of the great things to do too. Remember, we're trying to get rid of losing track of what was done and when. Also, if your commit has too many changes, you'll lose all of them, if you need to roll back to the previous version.
4. Make a habit of updating your branch with the changes from the Main branch frequently. This will allow you to have fewer conflicts when merging and you'll always see the latest version of the main design.