Git pipes long output into what’s called a pager by default, which can make it easier to view the output if it doesn’t fit on a screen. The ~ characters indicate that those lines were not in the original output, but it’s showing them so that you can scroll down past the bottom (i.e. the … Read more
As described in “How is git commit sha1 formed “, the formula is: (printf “<type> %s\0” $(git cat-file <type> <ref> | wc -c); git cat-file <type> <ref>)|sha1sum In the case of the commit 9eabf5b536662000f79978c4d1b6e4eff5c8d785 (which is v2.4.2^{}, and which referenced a tree) : (printf “commit %s\0” $(git cat-file commit 9eabf5b536662000f79978c4d1b6e4eff5c8d785 | wc -c); git cat-file … Read more
As ever, Git is right, it just has a quirky way of saying it: when you create a repository, the master branch actually doesn’t exist yet because there’s nothing for it to point to. Have you tried committing something after your git init? Adding a remote and pulling from it will also work, of course.
You should add .gitignore within each of your submodules. Since said submodules are like nested Git repo, they take care of their own ignore rules, and their status wouldn’t be influenced by the .gitignore of the parent repo (as explained here). For a vim-specific setting, as Randy Morris mentions in the comment, see the SO … Read more
It’s a bug in the documentation. Quote the asterisk with $ git add documentation/\*.screen or $ git add ‘documentation/*.screen’ to get the behavior you want. If instead you want to add files in the current directory only, use $ git add *.screen UPDATE: I submitted a patch that corrects the issue, now fixed as of … Read more
If by “checked out” you mean people who have cloned your project, then no it is not possible. You don’t even need to be a GitHub user to clone a repository, so it would be infeasible to track this.
It’s a bad idea to store any kind of plaintext secret in revision control, SSH private keys included. Instead, use ansible-vault to store the private key. ansible-vault can operate on any file type. Just encrypt the file with ansible-vault encrypt /path/to/local/private_key then install the key: – name: Install a private SSH key vars: source_key: /path/to/local/private_key … Read more
Looks like there are now several options for using git from node: gift: simple Node.js wrapper for the Git CLI with an API based on Grit (npm / github) node-git: a node.js git implementation modeled on grit (npm / github) nodegit: libgit2 asynchronous native bindings (npm / github) node-git: a thin wrapper around the command-line … Read more
git fetch origin; git reset –hard origin/<branch>
Muchas gracias to Bart’s Blog for this handy reference for svn branches in git. Apparently all I needed was to specify a remote branch when creating the git branch, e.g., git checkout -b git-topic-branch-foo foo where foo is the name of the remote branch.