This page provides info on recommended version control procedures in the
upgrade process and importing and merging new versions of Atoti Sign-Off.
Version Control System (VCS) Hygiene
We recommend committing an unmodified version of Atoti Sign-Off
before making any modifications.
Your repository should ideally be structured to take advantage of
built-in merge tools when importing Atoti Sign-Off upgrades. This can
be done by creating a branch which has the Atoti Sign-Off release
without any custom changes made to it.
Upgrading the Module
This section assumes you have used the above recommended VCS Hygiene.
Importing the new version of the Module
Check out the vendor branch from your VCS (this should contain the
Module the way it was delivered prior to any
customization).
Delete all the files from your local working copy
Copy in the new version of Atoti Sign-Off
Commit your local working copy as the new version. Make sure the
missing files are deleted from the repository and the new files are
added.
Your VCS repository now contains a copy of the new version of the
Atoti Sign-Off. More importantly, it is tracking the changes between
versions of Atoti Sign-Off.
Merging
Assuming the VCS branch containing your custom modification has a
previous version of the Module as an ancestor, you can use your
VCS tools to merge the latest release into the branch containing your
modifications.
The merge will take the diffs between the two versions of Atoti Sign-Off and attempt to apply them to the branch containing your
modifications.
There will almost certainly be conflicts; where both Atoti Sign-Off
and your project have changed the same code. The number of conflicts and
their complexity will depend on the nature of the changes to the
Module between versions, and how they interact with your custom
modifications. Your VCS tools will identify the conflicts and help you
to resolve them.
Once the merge is complete, your VCS should be able to tell you how the
project modifications differ from the Atoti Sign-Off release and how
your project code changed following the import of the latest version of
the Module.
