As the message says: no changes added to commit (use “git add” and/or “git commit -a”) Git has a “staging area” where files need to be added before being committed, you can read an explanation of it here. For your specific example, you can use: (note the extra a in the flags, can also be written as git commit … Read more
There are multiple problems the can cause this behaviour: Line ending normalization I’ve had these kinds of problems too. It comes down to git automatically converting crlf to lf. This is typically caused by mixed line endings in a single file. The file gets normalized in the index, but when git then denormalizes it again … Read more
Basic rename (or move): Case sensitive rename—eg. from casesensitive to CaseSensitive—you must use a two step: (More about case sensitivity in Git…) …followed by commit and push would be the simplest way to rename a directory in a git repo.
My team and I ran into this error, unable to update local ref, when doing a pull in SourceTree. Update 2020: Per @Edward Yang’s answer below, @bryan’s comment on this answer, and this question/answer you may need to run both git gc –prune=now and git remote prune origin. Running only the former has always worked for me but based on ppl’s responses … Read more
I ran into this issue with OSX. Original answer: It seems like a gpg update (of brew) changed to location of gpg to gpg1, you can change the binary where git looks up the gpg: If you don’t have gpg1: brew install gpg1. Updated answer: It looks like gpg1 is being deprecated/“gently nudged out of usage”, so you probably … Read more
The answer is there, git is telling you to fetch first. Probably somebody else has pushed to master already, and your commit is behind. Therefore you have to fetch, merge the changeset, and then you’ll be able to push again. If you don’t (or even worse, if you force it by using the –force option), you can … Read more
I have app servers that I bootstrap together using Chef + some ad-hoc bash scripts. The problem is, when I want to run an update on one of these app servers, I get: Do I really need to set this for doing a simple git pull origin master every time I update an app server? Is there … Read more
To add all the changes you’ve made: git add . To commit them: git commit -m “MY MESSAGE HERE” #-m is the message flag You can put those steps together like this: git commit -a -m “MY MESSAGE HERE” To push your committed changes from your local repository to your remote repository: git push origin master … Read more
–depth 1 is optional but if you only need the state at that one revision, you probably want to skip downloading all the history up to that revision.
It is possible to do (in the deployed repository) The fetch will download all the recent changes, but it will not put it in your current checked out code (working area). The checkout will update the working tree with the particular file from the downloaded changes (origin/master). At least this works for me for those … Read more