You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But when I try to sync with grit from A to B, I get errors that the files already exist.
error: .editorconfig: already exists in index
etc.
So I tried an empty repo - error: master branch not found.
So I added a file that didn't exist to it, and then tried syncing from A to B, this time got a different error - it copied commits from 2017 through July 2018, and then fails at one of them.
Any suggestions on best practices for getting initial sync going?
The text was updated successfully, but these errors were encountered:
This looks like to be exactly the type of tool I need, however, I'm getting some errors using it.
The monorepo has many projects, and has been developed since 2017.
I want to move each of those projects into separate repos, while still maintaining the monorepo for legacy CI purposes.
We will call the monorepo, repoA
I tried creating a new repo for just one of the projects to start with:
First I tried splitting it out initially using:
into a new repo, repoB
https://help.github.com/en/articles/splitting-a-subfolder-out-into-a-new-repository
But when I try to sync with grit from A to B, I get errors that the files already exist.
etc.
So I tried an empty repo - error: master branch not found.
So I added a file that didn't exist to it, and then tried syncing from A to B, this time got a different error - it copied commits from 2017 through July 2018, and then fails at one of them.
Any suggestions on best practices for getting initial sync going?
The text was updated successfully, but these errors were encountered: