A little help,
when you need it.

Start with the guides below. If you’re still stuck, email support@repodock.dev with your app version, Windows version, and the exact error message.

Git and GitHub setup

Use Set Up This Computer in RepoDock. It installs missing Git and GitHub CLI tools using winget or their official installers, then opens GitHub’s browser authorization. You approve Windows and GitHub prompts yourself. Managed computers may need administrator approval.

If setup cannot finish, keep the error message. You can also install Git from git-scm.com and GitHub CLI from cli.github.com, run gh auth login, and reopen RepoDock.

Push and pull

Push stages all changed files, creates a commit when needed, and uploads the current branch after typed confirmation. Review the Changed Files list and warnings first. Pull uses fast-forward only; RepoDock does not silently create merge commits.

If GitHub rejects a push because the remote has newer or unrelated history, review both repositories before proceeding. RepoDock does not force-push or resolve merge conflicts for you. If Git needs a commit identity, configure your preferred name and email through Git before retrying.

A moved folder or renamed repository

Use Change Local Path to relink a folder you moved yourself. It updates the saved path rather than moving files. Use Refresh GitHub Link after renaming a connected repository on GitHub. Disconnect removes only the local origin link.

Backups and device limits

Settings → Export Backup saves your project mappings, virtual folders, and preferences. It does not back up source files or include your license. Import replaces dashboard settings while keeping the current device’s activation.

A license allows two device activations. If you reach the limit after replacing a computer, contact support from your purchase email. Clearing the local license does not release an online device activation.

Latest release

1.0.9: Guided Windows setup now falls back to official Git and GitHub CLI installers when winget is unavailable or cannot finish installation.

Contact support

Include what you were trying to do and the exact error. For payment or license issues, include the purchase email and receipt reference. Don’t send card details, passwords, GitHub tokens, private keys, or project source code. Mask private paths and repository names in screenshots.