Related Content
Getting Started With Git Bisect
Git bisect is a git command that makes it easier to track down where a problem was introduced to a codebase.
In large projects you may find that a change was added to the code that causes a problem and you then need to track down where that problem occurred. Knowing where the problem was introduced makes debugging the issue a lot easier.
Getting Started With Git
I have been using Git for a number of years and I can remember feeling quite daunted at the complexity of some of the commands I saw on the internet. When I started using Git on a daily basis I soon realised that the basics were quite simple and the complexity only lay further down the road with commands like cherry-pick or rebase.
Git: Compare Differences Between Branches
The git diff command will allow you to view the differences in your workspace. This can be used in a number of ways to look at the differences in a file, in a branch or between two branches.
Committing The Composer Vendor Directory
When installing composer dependencies those dependencies are downloaded and stored in the 'vendor' directory.
Tidying Up A Git Repo
Creating branches in git basically free and is easy to do. This has lead to the development of techniques like git flow and other branch related work streams, which are now commonplace in development.
Find The Number Of Commits In A Git Repository
Use the following command to find out how many commits there have been in a git repository. Not really useful in itself, but an interesting figure to see how active a project has been over it's lifetime.
git log --oneline --all | wc -l
The following git log flags are in use here:
Add new comment