And then it showed up again, and again, and again-to the point that I was suddenly using Sudo for just about everything I did with Git. I felt somewhat accomplished for all of a few days, when suddenly the problem showed up again. Sure enough, I find myself on master, and I get on with my day: 'sharks don't look back because they have no necks necks are for sheep!' I said to myself, 'let's try Sudo' and see if that works: sudo git checkout master. 'Could it be that my user profile somehow has lost permission to use Git?'-I pondered.īeing in the hurry that I always am, I didn't take much time to read the actual output staring me in the face on my terminal. I thought to myself, 'wierd!?' and proceeded to stare at my terminal just long enough to loosely connect these permission problems with past use of Sudo completely unrelated to web work. When I ran git checkout master, Git gave me some business about not having the permissions necessary to unlink files. I don't recall the exact cause, but I do recall that one day I was trying to check out a local branch on my local machine: I think I was looking to get back onto Master (now known outside Acquia hosting as Main) from some branch I was fooling around with. We'll take a look at what happens, but let's start with how you might find yourself wanting to use Sudo with Git. Changing file permissions aside, if you'd like to overcome this, the easiest way to get past this is to use Sudo.Īn important note: on any Linux system, there will be files that belong to you (usually located within your user folder just below /home), and there will be files that belong to ROOT (often above the ~/user folder). Here's a classic example: there's a file you'd like to edit, but you don't have write access on the file (you open the file in an editor, but it doesn't want to save). With that said, there will be times when you need to assume the role of this super user-i.e., your user profile simply doesn't have the permissions necessary to get something done. This may not be a semantically accurate description of ROOT, but you can think of ROOT as a 'super user' on your computer: a user profile that has access to anything and everything. There's your user profile, and then there's the ROOT profile. Sudo at a Glanceįrom the get go, you need to understand that Linux systems limit the power of users by default. In the case of Git, however, it's anything but that. If you've been on the Linux command-line for any amount of time, you'll know that Sudo is a valuable tool for 'forcing' certain tasks. Sudo, at it's face, would seem like just another tool for coercing Git into compliance with your busy workflow. In the normal process of development, Git can occasionally get hung up for reasons not outwardly evident sometimes, rather than actually take the time to understand the complexities of Git, it's easier to just force your way through it. On certain occasions, it can be a strong temptation to use Sudo as a fix-for-all. In my case, outlined herein, the problem stemmed from a blatant abuse of sudo. This error is almost definitely a permissions issue. TL DR - check file permissions on Linux?-maybe don't use Sudo with Git!

Gitkraken reset profiles