On the git stash manpage you can read (in the “Discussion” section, just after “Options” description) that: A stash is represented as a commit whose tree records the state of the working directory, and its first parent is the commit at HEAD when the stash was created. So you can treat stash (e.g. stash@{0} is … Read more
The .gitignore file should be in your repository, so it should indeed be added and committed in, as git status suggests. It has to be a part of the repository tree, so that changes to it can be merged and so on. So, add it to your repository, it should not be gitignored. If you … Read more
In terms of source control, you’re downstream when you copy (clone, checkout, etc) from a repository. Information flowed “downstream” to you. When you make changes, you usually want to send them back “upstream” so they make it into that repository so that everyone pulling from the same source is working with all the same changes. … Read more
The error message error: refusing to update checked out branch: refs/heads/master is emitted by the remote repository and it means you’re trying to push code to remote non-bare repository that has different code currently checked out in the working directory. The best way to avoid this problem is to push to bare repositories only – … Read more
TL;DR A git rebase workflow does not protect you from people who are bad at conflict resolution or people who are used to a SVN workflow, like suggested in Avoiding Git Disasters: A Gory Story. It only makes conflict resolution more tedious for them and makes it harder to recover from bad conflict resolution. Instead, … Read more
Use git log –graph or gitk. (Both also accept –all, which will show all the branches instead of just the current one.) For branch names and a compact view, try: git log –graph –decorate –oneline
The –follow works for a particular file git log –follow — filename Difference to other solutions given Note that other solutions include git log path (without the –follow). That approach is handy if you want to track e.g. changes in a directory, but stumbles when files were renamed (thus use –follow filename).
Git can search diffs with the -S option (it’s called pickaxe in the docs) git log -S password This will find any commit that added or removed the string password. Here a few options: -p: will show the diffs. If you provide a file (-p file), it will generate a patch for you. -G: looks … Read more
Use git cherry-pick <commit> to apply <commit> to your current branch. I myself would probably cross-check the commits I pick in gitk and cherry-pick them with right-clicks on the commit entry there instead. If you want to go more automatic (with all its dangers) and assuming all commits since yesterday happened on wss you could … Read more
When you modify a file in your repository, the change is initially unstaged. In order to commit it, you must stage it—that is, add it to the index—using git add. When you make a commit, the changes that are committed are those that have been added to the index. git reset changes, at minimum, where … Read more