Both of the following scripts take the blob’s SHA1 as the first argument, and after it, optionally, any arguments that git log will understand. E.g. –all to search in all branches instead of just the current one, or -g to search in the reflog, or whatever else you fancy. Here it is as a shell … Read more
From the git-branch manual page: git branch –contains <commit> Only list branches which contain the specified commit (HEAD if not specified). Implies –list. git branch -r –contains <commit> Lists remote tracking branches as well (as mentioned in user3941992‘s answer below) that is “local branches that have a direct relationship to a remote branch”. As noted … Read more
The actual reason is that, in a new repo (git init), there is no branch (no master, no branch at all, zero branches) So when you are pushing for the first time to an empty upstream repo (generally a bare one), that upstream repo has no branch of the same name. And: the default push … Read more
Multiple GitHub accounts on the same computer?
Pat Notz is correct. You can get the commit back so long as it’s been within a few days. git only garbage collects after about a month or so unless you explicitly tell it to remove newer blobs. $ git init Initialized empty Git repository in .git/ $ echo “testing reset” > file1 $ git … 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
How do you create a new project/repository? A git repository is simply a directory containing a special .git directory. This is different from “centralised” version-control systems (like subversion), where a “repository” is hosted on a remote server, which you checkout into a “working copy” directory. With git, your working copy is the repository. Simply run … Read more
To see the diff for a particular COMMIT hash, where COMMIT is the hash of the commit: git diff COMMIT~ COMMIT will show you the difference between that COMMIT‘s ancestor and the COMMIT. See the man pages for git diff for details about the command and gitrevisions about the ~ notation and its friends. Alternatively, … Read more
Short Version Merge takes all the changes in one branch and merges them into another branch in one commit. Rebase says I want the point at which I branched to move to a new starting point So when do you use either one? Merge Let’s say you have created a branch for the purpose of … Read more
Yes, package-lock.json is intended to be checked into source control. If you’re using npm 5+, you may see this notice on the command line: created a lockfile as package-lock.json. You should commit this file. According to npm help package-lock.json: package-lock.json is automatically generated for any operations where npm modifies either the node_modules tree, or package.json. … Read more