FAQ & troubleshooting

Common questions, and the two things that trip people up.

Is it still git?

Yes. gitevolved shells out to your real, installed git and adds a remote transport. Every git command you know works.

Does git push origin still work?

Completely unchanged. Your GitHub (or GitLab, Bitbucket) remote is untouched. You can push to origin and to dosource:// side by side.

Does it replace GitHub?

No. Keep GitHub. gitevolved adds a smarter place to push to for parallel work; it doesn't take anything away.

Does it really never conflict?

No — and we won't pretend otherwise. Edits to different parts of a file merge automatically. Edits that genuinely change the same code still ask a human. gitevolved removes the false conflicts, not the real ones.

What needs the cloud?

Only dosource://cloud/<repo> (and a DOSOURCE_API_KEY). Everything else — recording operations, projecting files, exporting git commits, using a local op-log — runs offline with no account.

What languages does it understand?

Go has the deepest operation fidelity; TypeScript/JS, Swift, and others are supported, with a text-region fallback everywhere so it always works.

Troubleshooting

git-remote-dosource: command not found / clone fails on dosource://

The binary isn't on PATH under its exact name. Confirm git-remote-dosource --version runs; if not, add your install dir ($(go env GOPATH)/bin or ~/.local/bin) to PATH. Don't rename the binary — git derives the name from the URL scheme.

Cloud clone says unauthorized

Set DOSOURCE_API_KEY to a valid key (it's also read from a .vscode/dosource.json apiKey field if present).

License & contributing

Apache-2.0. Contributions under the DCO — sign off commits with git commit -s. See CONTRIBUTING.md.