Help Center
Clear, practical guides for writing, compiling, and sharing LaTeX projects.
Connect Git, GitHub, and WebDAV
Move project files through Git or synchronize them with GitHub and external storage.
Choose the right connection
Git, GitHub Sync, and WebDAV are separate Education/Plus/Pro tools. Reusable accounts, storage credentials, and Git tokens live in Account settings; each project is connected from the External connections view in its Activity Bar.
How to do it
- Use Git when you want the project on your own machine with your usual command-line workflow.
- Use GitHub Sync when the source of truth is a repository your team already reviews and releases from.
- Use WebDAV when the project has to land in institutional or personal storage rather than a code host.
- Nothing stops you from combining them, but decide which side you will treat as authoritative before you connect the second one.
Set up the connection
Each tool needs a credential created once in Account settings, then a per-project connection.
How to do it
- For command-line Git, open Access tokens in Account settings and create a Git token. In the project, expand Git, copy its repository URL or clone command, and use the token as the HTTP Basic password. Viewers can clone and pull; owners and editors can also make fast-forward pushes to main.
- For GitHub Sync, open External connections in Account settings, connect GitHub, and install the JointTex GitHub App for the repositories you choose. Then open GitHub in the project's External connections view, select an existing repository and branch, review the complete change preview, and confirm the manual synchronization.
- For WebDAV, save a reusable profile under Account settings › External connections using the root folder URL, username, and application password, or enter credentials for only one project. Choose a project folder, test the connection, review the first synchronization, and then connect.
- Use Sync now whenever you need to fetch remote-only WebDAV changes. Optional WebDAV automatic sync runs only after the JointTex project changes; three consecutive failures pause it until a manual synchronization succeeds.
Resolve conflicts and manage access
A conflict is never resolved behind your back, and connections follow the same roles as the rest of the project.
How to do it
- If GitHub or WebDAV reports a conflict, no files from that synchronization are changed.
- Open Review conflicts, compare both versions, choose which side to keep or keep both where offered, and submit every decision; JointTex rechecks both sides before writing.
- A project owner configures or disconnects GitHub and WebDAV; owners and editors can synchronize and resolve conflicts, while viewers can inspect status.
- Disconnect unused projects before removing a GitHub account or a WebDAV profile.