Guide · Open source
How to use git-tips: find everyday git commands fast
Updated · written with AI from the project's own documentation and checked against our catalogue data
git-tips is an MIT-licensed, JavaScript-based collection of common git commands, organized by topic and each paired with the task it performs. This guide shows you how to find a task, read its entry, and use the companion tools. It is aimed at developers and students who already know the basics of git.
Quick start
- 1Install git. Make sure git is installed on your machine, since it is the only prerequisite listed for this project.
- 2Clone the repository. Run the clone command from the README to download git-tips to your computer.
- 3Pick a topic. Open the table of contents and choose Basic Operations, Branching, or Log and History based on your task.
- 4Read the entry. Find the task title that matches your goal and read the command given for it before running it.
- 5Try the CLI if you want. Install the git-tip command-line tool from npm, or use the Docker container, to access the tips from the terminal.
What git-tips contains
git-tips is a reference document rather than a program. Each entry names a task you might want to do with git and gives the command that does it.
The entries are grouped under topics. The table of contents in the README lists three main ones: Basic Operations, Branching, and Log and History.
- Basic Operations: everyday tasks such as undoing local changes, rewording a commit message, and staging parts of a file.
- Branching: listing, renaming, tracking and deleting branches.
- Log and History: searching commits, viewing changes over time, and inspecting the version tree.
Clone the repository to read it locally
The README's install step is a single clone command. It downloads the repository so you can read the tips offline in your own editor or terminal.
You need git installed to run it. Prerequisites listed for this project are only git.
git clone https://github.com/git-tips/tipsFind a task by topic or by keyword
Start with the topic that fits your problem. If you want to undo something, look under Basic Operations. If you are trying to understand what changed, look under Log and History. Entries have plain task titles, so you can also scan the list for words like branch, commit, or stash.
Each title is a task, not a command name. That makes it easier to find a recipe when you know what you want to achieve but not the exact git syntax.
- Check the table of contents first, then open the topic section.
- Scan the task titles for the outcome you want.
- Copy the command from the entry and read it before running it in a repository you care about.
Read the interactive GitBook version
The README links to an interactive GitBook documentation site, which presents the same material in a browsable format. Use it if you prefer reading in a browser to scrolling a long Markdown file.
The project homepage points to the English README at the short git.io link.
Use the git-tip CLI or the Docker container
The README lists git-tip as a small command-line tool for using these tips from the terminal. It is linked to an npm package page, so it is installed through npm.
The README also links to a Docker container that packages git-tip. This may help if you do not want to install it directly on your machine.
Keep the version caveat in mind
The README states that the commands were tested on one specific older git release. Most common commands are stable, but newer git versions may add newer, simpler ways to do the same task. For example, the entries include a note about switching to a branch as a modern alternative to checkout.
If a command behaves differently on your git version, check your version's official git documentation before relying on it.
Add your own tip
git-tips is a shared list. The README asks people who want to add tips to read the contributing guide, which is linked from the top of the README as contributing.md.
What people use it for
- Looking up how to undo local changes or reword the previous commit message.
- Finding how to list branches already merged into master, or delete them.
- Searching commit history for a change, or viewing changes to one file over time.
- Learning which common git commands exist by reading through the topic lists.
Frequently asked questions
Is git-tips free to use?
Yes. The project is licensed under the MIT licence, as listed in the project details. You can read, clone and use it under those terms.
Do I need to install anything to use git-tips?
You need git to run the commands. To read the tips, you only need to clone the repository or open the GitBook documentation in a browser. The git-tip CLI is optional.
Does git-tips work with the latest version of git?
The README says the commands were tested on one older git release. Most common commands should still work, but check your git version's official documentation if something behaves differently.
Is git-tips a beginner tutorial for learning git?
Not really. Entries are short command snippets rather than step-by-step explanations of git concepts. Students new to git may get more from a full book such as Pro Git.
What are good alternatives to git-tips?
The project's comparable projects list includes Pro Git book, git-recipes, and Oh My Git. Pro Git is a full guide to git concepts, while the others focus on recipes or shortcuts.
How do I add my own tip to git-tips?
Read the contributing guide linked from the README, which is contributing.md in the repository. Follow its instructions for submitting a new entry.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
git-tips suits developers who already use git and want quick, topic-based recipes for everyday tasks, and students who want to see many common commands together. It is not the right choice if you need to learn git concepts from scratch, want software to install, or need guidance verified on recent git releases.
Install options & downloads