![onedrive for mac says it onedrive for mac says it](https://www.multcloud.com/screenshot/en/others/onedrive-mac-general-sync.png)
~/github/rentap.js M % git commit 'figured out some more stuff with the forms in views and started figuring out row and mode in models so also made matching routes and controllers'Įrror: pathspec 'figured out some more stuff with the forms in views and started figuring out row and mode in models so also made matching routes and controllers' did not match any file(s) known to git.
![onedrive for mac says it onedrive for mac says it](https://cdn.mos.cms.futurecdn.net/C9QY5eDcXPsTxQ2wGtagcV.jpeg)
Turns out, it was an error message because I forgot -am. I was working on autopilot with git commit and git push, and hadn't read the output from git commit. So no startup for this one, I will have to sync manually. A partial solution: Closing OneDrive app or pausing will do, but I can not sync. If you have no idea why you would have a detached head, then you probably don't. I guess MS has not really thought it through. My mistake was different than everything so far mentioned. If you did this by mistake, you can ask the reflog for HEAD where you were, e.g. git checkout master), and a later git prune or git gc would garbage-collect them. What this means is that you can discard your temporary commits and merges by switching back to an existing branch (e.g. The state you are in while your HEAD is detached is not recorded by any branch (which is natural - you are not on any branch). You can even create a merge by using git merge $othercommit. You can make changes and create a new commit on top of a detached HEAD. You can use git reset -hard $othercommit to further move around, for example. You can use all git commands while in this state. The most obvious example is to check out the commit at a tagged official release point, like this: $ git checkout v2.6.18Įarlier versions of git did not allow this and asked you to create a temporary branch using the -b option, but starting from version 1.5.0, the above command detaches your HEAD from the current branch and directly points at the commit named by the tag ( v2.6.18 in the example above). It is sometimes useful to be able to checkout a commit that is not at the tip of one of your branches. # reset your branch head to your previously detached commitĪs mentioned in the git checkout man page (emphasis mine): After renaming it, and restarting the sync process, everything started working. Warning: the following does a git reset -hard: make sure to use git stash first if you want to save your currently modified files. I logged on via the browser, and found a file that was of corresponding size, and had been modified recently by another user. Indicating that your latest commit is not a branch head. Are you working with a detached head by any chance?