I see it every day, beginners have a hard time picking up git. Aside from the DSCM concepts, the command line is not easy: it is aimed at people who know git.. advanced nerds, not beginners.
This project is an attempt to make the git command line a friendly place: it eases the learning process by providing guidance and high level commands.
- g2 will save you time by providing hight level commands.
- g2 is generally safer than git as it prompts before destructive actions.
- g2 helps setup git settings : sshkeys, username, email and tools.
- g2 provides two letter acronyms for most commands.
- g2 eases the merge process.
- g2 provides a reduced set of commands which give guidance on what to do next.
- g2 enhances command line experience auto-completion and a smart prompt.
- g2 warns when a branch history was changed on the server (forced pushed).
- g2 checks the freshness of the branch prior to merging and warns accordingly.
- g2 enforces a clean linear history by introducing new commands.
- g2 requires a clean state before rebasing, checking out, branching or merging.
- g2 provides guidance when it cannot perform an operation.
- g2 brings a number of friendly commands such as : panic, sync, freeze, wip.
- g2 eases branch creation.
- g2 is just easier at undoing things.
- A replacement for git. Rather, g2 is a layer on top of git
- A magic way to learn GIT. It will help by providing guidance but you still need to understand how git works.
- g2 is a layer on top of git, If you are doing a manual install, a recent version of git must be pre-installed.
- Please backup your favorite ~/.gitconfig as g2 with recreate it from scratch.
- For now G2 only runs on bash
Please clone the repository, edit either /etc/bashrc, /etc/bash.bashrc or ~/.bashrc and add the following code:
[[ $PS1 && -f /path/to/g2-install.sh ]] && \ . /path/to/g2-install.sh
Same as Linux, make the change in
The software will soon be available via a HomeBrew package, stay tuned.
Add the following script to /etc/bashrc or ~/.bashrc (or any other file sourcing those).
PATH=/usr/xpg4/bin:$PATH export PATH [[ $PS1 && -f /path/to/g2-install.sh ]] && \ . /path/to/g2-install.sh
Git is not a prerequisit on Windows as the installer comes bundled with it.
Please download the Windows native installer from this link.
The project introduces the
g alias. Taken without parameters it displays the following output.
$ g Usage: abort - aborts any rebase/merge am <?-f> - amends last commit with staging area br <?-D> <?-M> <?branch> - list or create branches bs - bisect co <branch> - switches branch (either local/remote) continue - resumes a conflict resolution cp <commit> - cherry-pick ci <?params...> - commit clone <url> - clone a remote repository df/dt <?params...> - compares files fetch - synchronizes remote branches freeze/unfreeze <?-m comment> <?file> - freeze/unfreeze files gc - garbage collects: run fsck & gc gp - grep gui - launches the GUI ig <file> - adds to gitignore & removes from source control init <folder> - init a repository key <?-gen> - displays/generates your ssh public key mg <?params...> <branch> - merge mt <?params...> - fixes conflicts by opening a visual mergetool mv - move (rename) a file lg - displays commit log ls <?params...> - list files under source control panic - gets you back on HEAD, cleans all untracked files pull/push <?opts> <remote> <branch> - deals with other branches rb <?params...> <branch> - rebase rm <params...> - remove rs <params...> - reset rs 'upstream' - resets branch to upstream state rt <?params...> - remote rv <commit> - revert setup - configures user, key, editor, tools sh <?-deep> - show commit contents sm <?params...> - submodule ss <?params> - stash st <?params...> - status sync - syncs working branch: fetch, rebase & push tg - tag track <?upstream_branch> - shows/set tracking undo file|'commit'|'merge' wip/unwip - save/restore work in progress to branch
On top of providing two letters acronyms for most git commands, g2 has interesting features which enhance command line experience.
Let's start with the "sexy" one: the g2 prompt.
The prompt shows:
- The current branch name and the hash of the last commit. M is used as a subtitute for "master"
- File counts: staged, changed and untracked filed.
- Obviously username and host.
- And finally the path, which smartly truncates at 40 caracters.
- The prompt colors will adjust depending of the state of the repositoty: clean, modified, comflict resolution... etc
- Not visible on this screenshot is the optional error code should a shell command fail.
Note: file counters can be expensive with large repositories. You may turn off the feature by running
g setup and setting "Count files in the bash prompt? (true):" to false.
So here you go, you downloaded git for the first time and I bet you are stuck on the ssh key generation. git is so lame and user unfriendly.
allright, with g2 this is how it works:
g setupand answer the questions.
- that's it!
At anytime in the future, you may display your ssh public key with:
g key. copy/paste it into github. You are done.
Should you need to regenerate the key pair, the process is equally user friendly: use
g key -gen
Git is often referenced as a content SCM that freezes the state of the repository on every commit. So rather than providing the rather granular commands
git add and
git rm commands, g2 introduces
g freeze literally freezes the state of the workspace into the staging area. Should you need to freeze just one file, or one folder, use
g freeze <path>.
There is also a handy one way command
g freeze -m "msg", that skips the staging area and commits directly.
Equally straightforward is the
g unfreeze command, which unstages the files form the index back into the workspace.
The contents of the staging area can be committed with the
g ci -m "msg" command. No rocket science here, you may however like the
g undo commit command that reverts the last commit
I would recommend a look at the cheatsheet to better understand how these commands work: CheatSheet
Since we introduced undoing in the previous section, let's cover it all.
g2 comes with the following undo scenarios:
g undo commit- undo the last commit, put changes back into the staging area
g undo merge- reverts all commits up to the state before the last merge
g undo myfile.txt- reverts the changes in myfile.txt with the version from the repository.
It's so easy to get lost when starting git! Working with beginners, I found that an easy way to keep them focused is to provide visuals. Now this is not the github network graph, but it's close enough to get them focused. Type
g lg and enjoy the enhanced colorized commit log output.
Learn to read that tree, it's important: it holds the commit history for the current branch.
Since we are talking about history, I should probably mention that g2 will ALWAYS prompt before running any destructive actions.
It happened to all of us. You try a new command (like a rebase) and things don't work as expected: git complains on every commit attempt, the prompt shows a weird stauts. Suddenly, you feel the urgency to hunt an expert advise: you start hunting the closest git-master: bad luck he's not around! In fact there is no-one to help you! "Damn it ! I wish I never run that command!", you start pulling your hairs and screaming "CVS was so much bettttttter!"
Well, you are panicking… and we built a command especially for you:
panic when you feel like getting help from your git master. It checks out the last known good state (HEAD) and removes all files not under source control, leaving a clean workspace to resume from. It's the easiest way to get you back on track and ready to work. No more cold sweats and your git-master can rest.
Displaying the list of branches is achieved with the branch command:
g br. Note how it provides details not only about the local and remote branches, but also about the state of these branches when compared to the status on the server.
$ g br gh-pages * master remotes/origin/HEAD -> origin/master remotes/origin/gh-pages remotes/origin/master --- gh-pages (ahead 0) | (behind 0) origin/gh-pages master (ahead 0) | (behind 0) origin/master
Given a parameter, the command creates a new branch. g2 walks you though the steps that will typically take git 3 to 4 commands.
g co NEW_branch to switch to that branch.
$ g br NEW_branch gh-pages * master remotes/origin/HEAD -> origin/master remotes/origin/gh-pages remotes/origin/master --- gh-pages (ahead 0) | (behind 0) origin/gh-pages master (ahead 0) | (behind 0) origin/master $ g co NEW_branch Switched to branch 'NEW_branch' $
If you are familiar with git, this is no rocket science. There is however a hidden gem which might save you headaches going forward: g2 is extremely strict when it comes to switching branches: it only works from a stable state.
A stable state means: no modified files, no staged files. Should you have any changes, g2 will complain with the following message:
fatal: some files were changed on this branch, either commit <ci>, <wip> or <panic>.
While based on git, g2 enforces a simplier merge flow.
So what commands can get you into merge mode? Well the ones that merge contents:
cherry-pick to name just a few. Merging with git is a revolution compared to other source control systems, most of the time it happens auto-magically. But in a few instances, you will need to resolve conflicts manually.
When this happens, g2 will stop the command flow. Let me enphasize what that means:
- If you are merging, a conflicts will stop before the final commit.
- If you are rebasing or syncing, a conflicts will stop on the current replay step.
You may resolve conflicts by issueing a
g mt (mt=mergetool). The default visual mergetool will show up and let you resolve each conflicting file manually. Typically, you will see your file on one side, the file you are merging with on the other and the common ancestor. The common ancestor is here to quickly pick what happened to the file: you can quickly pick additions and removals.
Once conflict resolution is completed, the merge process needs to be resumed manually.
Now, If you are a git expert, you know that there are actually 3 commands to resume form the 2 scenarios above. git makes it so confusing, doesn't it?
With g2 we simplified the process: no matter what flow you are in, there is only one command to resume:
g continue. That's it!
Finally I should probably mention
g abort that cancels an ongoing merge/rebase and reverts back to the state prior to the merge attempt.
The whole concept of tracking is broken in git. It's not so much the feature, it's the way it is typically explained. All beginers wonder "What the hell is a tracking branch and how is it different from a regular branch?"
Backup… let's start from the beginning, the g2 way this time:
Most G2 commands only apply to the branch you are in, there is no magic updates happening behind the scene: for instance, when you get changes from the server, they only apply to your current branch.
Please type the following command:
g track, you should see something as such:
That's the tracking table. the first sections shows how each local branch is linked to its upstream remote/branch. In other words, what you see is the mapping between your local branches and the ones on the server(s). clear?
Ok... and now what?
Well tracking is used accross several commands in g2, the most common one is
g sync which you will learn in the next section. But you can also issue a
g reset upstream or a
g diff upstream. Even when you create a branch, g2 reads to current tracking to figure where to create the remote branch.
Note that it is also common to see branches with no upstream branch, in which case you may use
g track remote/branch to enforce the mapping.
Before introducing one of the main g2 features, let me talk about what NOT to do when merging with git.
Please have a glance at these graphs taken from various projects on github. Note how the branches overlap and how these loops make the graphic extremely difficult to read as the number of commiters increases.
Looks familiar? Wouldn't it be nicer to have straight lines, with segments showing only when feature branches are merged in? As such...
The above graph is 30+ developers working together on about 20 active feature branches. Note how the graph is clean an easy to read. Two types of flows… the work on the branch itself, and merging contents/features from others, we will get back on this in a minute.
In order to achieve this result, g2 enforces two different merging scenarios, each backed by a different command:
- Saving the code in the working branch, that's what we do most of the time
- Merging features from other branches, like merging the latest changes from production.
The matching commands are
g sync and
g pull, here is how to use them:
g syncto synchronize the current branch. The command doesn't take any parameters because it uses the tracking table to figure the remote/branch. To enforce a clean linear history, the changes are always appended to the end of the branch. Once completed, the changes are sent back to the server.
For the git expert, the command issues a fetch, a rebase and a push with a multitude of validations in between. For instance, it will block if the remote history was force updated; also it won't push a wip commit (see below).
g pullwhen merging contents from a feature branches.
Note: g2 also supports
g sync upstream which only fetch and rebase, handy with read-only clones ;-)
Saving the work in progress is a common task: Typically, git stash comes to the rescue. The issue with stashing is that you typically loose track of which branch it was created from. Stashing is indeed a short term solution.
unwip. Two handy commands that you will learn to love. Unlike stashing, wip commits the work in progress as a regular commit.
$ g st ## master MM README.md M g2-prompt.sh (M=000f0 +2 *1) orefalo@OLIVIERS-IMAC $ g wip [master 0dcbfb3] wip 2 files changed, 31 insertions(+), 13 deletions(-) (M=0dcbf) orefalo@OLIVIERS-IMAC $ g lg * 0dcbfb3 - (HEAD, master) wip (5 seconds ago) <Olivier Refalo> * 000f060 - (origin/master, origin/HEAD) fix freeze and wip (5 hours ago) <Olivier Refalo> * b44487e - adding gui & freeze -m (6 hours ago) <Olivier Refalo> * 7acd770 - documentation, removed undo (24 hours ago) <Olivier Refalo> * a248217 - first commit (3 days ago) <Olivier Refalo> * 5fa2c06 - initial commit (3 days ago) <Olivier Refalo> $ g unwip Unstaged changes after reset: M README.md M g2-prompt.sh $
But unlike commits, wip commits CANNOT be merged, pushed or synched. You cannot commit on top of them either.
In orther words, a wip commit in meant to stay at the tip of the branch until you are ready to
unwip and resume your development.
For convinience, several commands have been enhanced to accept the "upstream" keywork. As discussed earlier, the upstream is the on the server that syncs with your local branch. To see tracking setting, just enter
- g rs upstream - resets the current branch to the state of the upstream (read the state of the branch on the server)
- g merge upstream - merge local branch from the contents from the upstream
- g sync upstream - pull contents from the server, rebase but DON'T push
Please refer to the cheatsheet.
gis the command and it obviously comes from git
2because most of the actions are two letters long.
No, g2 doesn't enforce any branching policy.
- From a source control standpoint, yes g2 is interopable with git.
- From a command line parameters standpoint, definitly NOT. g2 grammar is simplified and hence doesn't support all the options available in git.
To ensure the git configuration is in a stable, known state.
Please notify us via the project issue tracker. For the time being, please use
$GIT_EXE to run the real git command.
Author: Olivier Refalo
- Contains a modified version of git-prompt - Leonid Volnitsky
- Contains a modified version of git-completion.bash - Shawn O. Pearce
- GUM by saintsjd. Wonder why this project feelt short on delivery.
- Andrew Peterson/ NDP Software for their cool interactive Cheatsheet
- The mainteners behind msysgit who made git on windows all possible
Distributed under the GNU General Public License, version 2.0.
- doc: provide basic guidance on how a commit is performed using g2
- doc: add typical solutions:
- doc: talk about gc
- doc: talk about g am
- g mode - for advanced users
- g as - aliasing
- g undo needs more validations
- enforce completions for undo *, and all the upstream commands
- upgrade g2-msys to 1.7.11
- fix little issue with undo,freeze,dt,ig
- g rv wasn't working
- g dt upstream
- g rb upstream
- g df upstream
- g mg upstream
- g2 completion - merged with upstream git 1.7.11 completion
- completion, rename __git to avoid conflicts -> cancelled: probably better this way
- g version
- add doc about, g sync upstream + completion
- g sync upstream
- sm - not working
- g undo merge = reset --hard ORIG_HEAD
- g ss/stash
- g undo file
- g undo commit
- g undo commit -f