When you start a run or workspace in a project, any repositories added to the project are cloned into
/repos and will have the branch or commit you specified checked out.
Remember that your Domino working directory is in
/mnt, which is a sibling of
/repos. Both directories are in the filesystem root (
/). Scripts you have added as Domino files can interact with the contents of these repositories by specifying an absolute path to
When you start a Workspace session in a project that has added Git repositories, you will see those repositories listed in the Session Overview under Git Repository. If you make changes to the contents of those repositories while running the workspace, those changes will be itemized file-by-file under each repository.
If you want to commit those changes back to the repository, click the checkbox next to the repository name and then click Full Sync.
You will be prompted to supply a commit message. This commit message will be attached to commits to the selected Git repositories, and to a new revision of the Domino project if there are changes to Domino files. Git commits will be pushed to the default branch you specified when adding the repository.
If you attempt to stop your workspace while there are uncommitted changes to your Git repositories, you will be prompted to commit those changes. This works the same as the Session Overview interface. Click the checkbox next to the repositories you want to commit to, supply a commit message, and click Stop and Commit.
If you try to commit when there are conflicts between your local changes and the state of the default branch in remote, Domino will create a new branch from its local state. Domino will then push that new branch to remote.
After this happens, you will need to resolve those conflicts outside of Domino or use the command line in your Workspace session to resolve them. The next time you launch a Workspace session, Domino will check out the default branch from remote, not the new branch it pushed.