I run the wizard to add a GitLab repo. All steps through the wizard are successful, but after saving, it starts the wizard again. I close the wizard, and click "Save" in the top right corner. It starts the wizard again. When trying to leave, it warns for unsaved changes. There is no local .git subdir in my user folder. There was before, but I had to remove it to get rid of the "unrelated histories" error message. I expected it to be re-created, but it isn't.
Update: Removed entire Grav project and recreated from scratch. This time connected to GitHub instead of GitLab. Same result. Note that I do get a successful login popup when testing the connection.
Update 2: Another thing where I may deviate is that I am running Nginx instead of Apache. This is the config snippet:
Hey @jkransen , a new release v2.1.1 is out and should address a regression introduced that would cause that unrelated histories error you were seeing.
I run the wizard to add a GitLab repo. All steps through the wizard are successful, but after saving, it starts the wizard again. I close the wizard, and click "Save" in the top right corner. It starts the wizard again. When trying to leave, it warns for unsaved changes. There is no local .git subdir in my user folder. There was before, but I had to remove it to get rid of the "unrelated histories" error message. I expected it to be re-created, but it isn't.
Git Sync 2.1.0 Remote Git repo: gitlab.com Grav 1.6.25 Grav Admin 1.9.14
Update: Removed entire Grav project and recreated from scratch. This time connected to GitHub instead of GitLab. Same result. Note that I do get a successful login popup when testing the connection.
Update 2: Another thing where I may deviate is that I am running Nginx instead of Apache. This is the config snippet:
Update 3: It is a private repo, but I assume that doesn't make a difference, as it can connect with the provided token.