What are some best practices for using Copia while commissioning?

Below are some best practices that can be used during the commissioning phase of a project:

Branching and Merging

• Commissioning Branch: A new branch, named Commissioning, should be created from the main branch, which should be kept up-to-date with all changes.
• Pull Request: Upon completion of commissioning, a Pull Request should be initiated to merge the commissioning changes back into the main branch. The main branch should not have changed while the Commissioning branch was open. 

Committing

• Daily Commits: A minimum of one commit should be made to the commissioning branch at the end of each day. Commits can be made without internet connection, and they can be pushed once connection is re-established. 
• Commit Messages: Write clear, descriptive commit messages. This practice is vital for understanding the history of the project and for quick reference in the future.

Additional Features

• Issue Tracker: The issue tracker is essential for tracking bugs and missing features identified during the commissioning process.
• Tags or Releases: Use Tags or Releases for marking release points. This is especially useful during commissioning for tracking versions that go into production.

 

You can find more information about the above functionality in our Documentation.