cknadler / git-feats Goto Github PK

Regardless of configuration, completing a feat will always post to gitfeats.com. This should only happen when the user has, what seems like, a proper configuration.

I'm assuming gitfeats is running on the free heroku.

Heroku will store unvisited sites and then hang when someone attempts to hit them for the first time. The problem is that when I go to issue a git command the api upload portion will hang for awhile, and block me from my work.

I think the solution here may be a thread spawn to keep the IO from blocking.

Very similar to #10.

Usage:

$ git feats history

# display a table of the git command history

Right now, when the gem "udpates" your feats, ie. posting to gitfeats.com, the response from the post is ignored. If the response is anything other than 200 there should be error handling on the gems side. This ties in with the need for a better api on gitfeats.com.

I'm a big fan of YARD and its structure. I'm all for keeping the docs out of the repo, but I think a comment format should be used. Thoughts?

http://yardoc.org/

fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
git version 1.7.12

Got this today trying to use git status. I think issues like this should be more "telling" or at least give more details to what's going on.

For the same reasons that defunkt/hub recommends you install with homebrew.

Usage:

$ git feats list

+---------------------+
|       Feats         |
+---------------------+
|    Status Report    |
+---------------------+

Display a table of the users completed feats.

Use terminal-table to display the table.

This is a post test suite feature.

git-feats should work on all ruby versions past 1.8.7.

Add support for hub and hub specific feats.

Looks like your domain is expiring.

Putting the API key in ~/.gitconfig wont allow you to track that file with git for a dotfiles repo.