Pushing a new branch to a repository’s remote often requires two attempts by the scatterbrained developer, but there is help in push.autoSetupRemote.

The .gitignore file in a Git repository serves as a configuration file that specifies files and directories that Git should — as the name implies — ignore. When Git encounters a file or directory listed in .gitignore, it automatically excludes them from being tracked, preventing them from showing up in commands like git status and git add.

Every now and then my inbox in Github shows x total unread updates without having actual updates. When I click on it, there are no unread notifications. This is a known issue and it’s been around for a while. The notifications are called “ghost notifications” and they are not visible in the UI.

If you are like me you probably typed more than once git stash and meant git stash list while working on many different things at the same time. If not, then feel free to go somewhere else and don’t waste your time here :]

Despite its many advantages and nifty features of Git, there’s one feature it lacks: a status hook. In Git, hooks are scripts that I can execute automatically at specific points during the version control process. These hooks perform custom actions, such as running tests, enforcing coding standards, or sending notifications, at various stages like pre-commit, post-commit, and post-merge.

Every now and then I find myself in the situation of needing to tidy up my projects and remove large amounts of local and remote tags in my Git repositories. The procedure is not too hard, but I have to look it up again each time, so why not just writing it up.