Change Tracking

Once a repository is setup, changes can be developed as usual via the Jade IDE.

As changes are made, they're added to the list of pending changes for the current branch, which are displayed at the bottom of the JadeGit Changes explorer.

When ready, these may be committed with a message entered above, committing either all changes, or specific changes staged beforehand (via context menu for selected changes).

When changes are being staged, they're extracted from Jade, during which errors may be raised referring to unknown entities. These highlight entities which haven't been extracted/staged previously. These may need to be updated and/or staged explicitly before dependent changes can be staged.

Loading Changes

Schema files may be loaded as normal via the IDE, changes within which will be tracked like those made directly. The schema files shouldn't require any amending beforehand, assuming they contain the schema entity modified by details that are generally included by default (needed for Jade to invoke the patch control hooks used by JadeGit for change tracking).

Form changes are not currently tracked during a schema load as expected. This is due to a platform issue (PAR 70027), where the hooks JadeGit depends on are not being called in this scenario. To workaround this issue, after loading any form changes, open/save updated forms via the painter for changes to be tracked.