You can now pass --learn to any GitHub gem command to see the git operations being run under the covers.
--learn
git
Hot off the presses:
$ gh fetch schacon —learn Fetching schacon/master == git fetch schacon master:refs/remotes/schacon/master == git update-ref refs/heads/schacon/master refs/remotes/schacon/master == git checkout schacon/master warning: refname ‘schacon/master’ is ambiguous. Switched to branch “schacon/master” $ gh fetch_all schacon —learn == git fetch schacon $ gh clone schacon/grit —learn == git config —get github.user == git clone git://github.com/schacon/grit.git Initialized empty Git repository in /Users/chris/Projects/github-gem/grit/.git/ remote: Counting objects: 3369, done. remote: Compressing objects: 100% (2107/2107), done. remote: Total 3369 (delta 1229), reused 3355 (delta 1216) Receiving objects: 100% (3369/3369), 1.80 MiB | 140 KiB/s, done. Resolving deltas: 100% (1229/1229), done.
As always:
$ gem install defunkt-github
Want to contribute? Dive into the commands and join the long list of contributors.
With this latest release, the network command went away (reverting back to 0.2.1):
dhcp-14:/tmp/github-gem 539% github network commits git: ‘network’ is not a git-command. See ‘git —help’.
Nice catch – thanks Dustin. I just pushed out a new release with a fix (was a faulty Manifest).
With this latest release, the network command went away (reverting back to 0.2.1):
dhcp-14:/tmp/github-gem 539% github network commits git: ‘network’ is not a git-command. See ‘git —help’.
Nice catch – thanks Dustin. I just pushed out a new release with a fix (was a faulty Manifest).