Jamdesk Lets Teams Edit Docs Locally and Skip GitHub Entirely
Jamdesk's Nov. 7 update adds jamdesk pull for local editing, GitHub-free publishing and auto-fix commits for build warnings.

Jamdesk now lets a team download its docs as a git repository, edit them on a laptop and publish with one command, and it no longer requires a GitHub account to start, according to the company’s Nov. 7 changelog. The same update adds an auto-fix mode that commits corrections after each build.
Local editing with jamdesk pull
jamdesk pull downloads a site’s docs as a git repository, and jamdesk deploy publishes the edited copy. Jamdesk said the local copy can be edited by hand or with an AI coding agent such as Claude Code. The command needs CLI 1.1.227 or later. If the docs changed in Jamdesk after the last pull, jamdesk deploy warns about the conflict, and pulling again merges the dashboard changes into the local copy.
Publishing without GitHub
New sites can skip GitHub at setup by choosing “Continue without GitHub.” Jamdesk then keeps the docs in a private repository that the team edits in the dashboard editor. A “Move to GitHub” action later copies the docs and their full history into a repository the team owns, on any plan. Jamdesk also added a verification path for teams whose GitHub account is already tied to another Jamdesk account: they can prove ownership on GitHub and connect the repositories they can push to.
Auto-fix for build warnings
With AI Fixes set to Auto-fix in settings, Jamdesk commits fixes for links, titles and descriptions after each build. Every run appears in Build History with an Undo button. jamdesk ai-fix changes the setting from the CLI, and jamdesk fix --json hands the list of fixes to an AI agent. The CLI commands need version 1.1.229 or later.
Smaller additions
Password-protected sites can show a “Sign in with Jamdesk” button when allowMembers is true, so team members use their own accounts while outside readers keep the shared password. That option requires a paid plan. Sites can also add a copyright line to the footer, set a footer per language and style it with stable CSS class names, which needs CLI 1.1.231 or later. Banners gain amber and red styles, with a separate banner per language.
Key takeaways
jamdesk pullandjamdesk deploygive Jamdesk a local, git-based editing loop; conflicts are flagged on deploy.- New sites can start without GitHub and move to a repository later, with full history, on any plan.
- Auto-fix mode commits link, title and description fixes after each build, and each run can be undone.
- Team sign-in for password-protected sites requires a paid plan.
The take
We think the local-editing loop matters more than the GitHub-free setup. A docs host that only offers a browser editor leaves out the way many writers now work, which is to point a coding agent at a folder of files. Handing over a git repository lets that agent use the same tools it uses everywhere else. The undo button on auto-fix commits is the right safeguard, because a tool that rewrites titles and descriptions on its own should be easy to reverse. We’d turn on Auto-fix for a week and read the Build History before trusting it on a site where titles drive search traffic.


