πŸ”€Version Control

Branches

Once you add a Module to a project (see Adding .fmp12 files to a project), a copy of your file will be placed on your main branch, named <filename>_main.fmp12. This branch has the most up-to-date working versions of your solutions, and ideally, these should not be touched. Instead, create branches from main to make modifications.

Start by creating a dev branch to work on. As you become more familiar with this workflow, use branches to test or stage changes in isolated environments without affecting the development file. If needed, you can always delete a branch and its associated files.

Versions

During development, create a Version whenever you want to save a particular state of your file, effectively making either a clone or full backup. Think of a Version as a snapshot of your file at a specific point, allowing you to revert back to this state if future changes cause issues. When making a Version, you can document the changes and, optionally, specify a version number. This process ensures you have a recoverable point to return to in case of any unintended alterations or errors.

Last updated