I ran dgit init and just hit enter at this prompt because the "Y" was capitalized (indicating it was the default response if none was given). However, the output after that was:
You are setup and ready to roll with dgit.
Just use git as you usually would and enjoy a fully decentralized repo.
If you would like to clone this dgit repo on another machine, simply run 'git clone dgit://quorumcontrol/dgit-test-repo-wes3'.
If you use GitHub for this repo, we recommend adding a dgit action to keep your post-PR branches in sync on dgit.
You can find the necessary action here:
https://github.com/quorumcontrol/dgit-github-action
Finally for more docs or if you have any issues, please visit our github page:
https://github.com/quorumcontrol/dgit
But git remote -v indicated there were no remotes configured.
However, running dgit init again and answering the Is that ok? prompt with y instead produced this output:
Success, dgit is now accessible under the 'dgit' remote.
'git fetch dgit' will work flawlessly from your decentralized repo.
You are setup and ready to roll with dgit.
Just use git as you usually would and enjoy a fully decentralized repo.
If you would like to clone this dgit repo on another machine, simply run 'git clone dgit://quorumcontrol/dgit-test-repo-wes3'.
If you use GitHub for this repo, we recommend adding a dgit action to keep your post-PR branches in sync on dgit.
You can find the necessary action here:
https://github.com/quorumcontrol/dgit-github-action
Finally for more docs or if you have any issues, please visit our github page:
https://github.com/quorumcontrol/dgit
That "Success..." bit was unique to the second run. And after this run, git remote -v showed a dgit remote had been created.
I ran
dgit init
and just hit enter at this prompt because the "Y" was capitalized (indicating it was the default response if none was given). However, the output after that was:But
git remote -v
indicated there were no remotes configured.However, running
dgit init
again and answering theIs that ok?
prompt withy
instead produced this output:That "Success..." bit was unique to the second run. And after this run,
git remote -v
showed adgit
remote had been created.