Frequently Asked Questions for Version Control#
How am I supposed to do manual Git on a remote project repository?#
This is a great question, and there are a few ways to do it.
Git is installed in the project container, and all of your Git configuration is passed there.
Open JupyterLab in the project container and use Git in the terminal there
Use Git versioning in VS Code if you’ve added it to the project
Hint
You can also use the Workbench CLI to attach your local terminal to the remote project container and use Git there.
Run the following command to see how:
nvwb attach -h
Why can’t I clone a project using standard git clone?#
AI Workbench requires creation and tracking of project-specific metadata during cloning, which standard Git clone does not capture.
For example, Workbench creates an entry for the project in $HOME/.nvwb/inventory.json, as well as information about the container build and other environment metadata for the project. That information goes into the folder $HOME/.nvwb/project-runtime-info/<project-name>-<hash>/.
This metadata is required for Workbench to properly manage the project and provide various features.
Why can’t I clone a regular Git repository with Workbench?#
AI Workbench requires specific files and folders within the repository, such as .project/spec.yaml to provide the various features.
Repositories that include required files are recognized as AI Workbench projects (How to Work with AI Workbench Projects).
If you try to clone a Git repository in Workbench that doesn’t have the required files, Workbench will not be able to recognize it as a project and will return an error.
However, you can make any repository compatible by adding the necessary files and folders. For details on structuring repositories for AI Workbench, see Project Structure.