Running it
Then it joins your version control
Point it at a repository and the architecture inherits everything your code already has: history, review, blame and rollback. Nothing about the way you work has to change.
- 02It commits, it never mergesArchMeta commits your edits and pushes when you configure it to. It never merges, rebases or branches behind your back.
- A divergence is reported, not resolvedIf the history has moved apart it stops and says so, rather than leaving conflict markers inside your model.
- Inert without a remoteNo repository or no upstream, and the behaviour is byte for byte what it was. The solo setup never pays for the team one.
- Your history, your serverGitHub, GitLab, Bitbucket, or a Git server in your own datacentre.