From 9cf0722fc7933d0df5ece6b06a79e4b96b8084d1 Mon Sep 17 00:00:00 2001 From: Eric Date: Tue, 30 Apr 2013 00:27:06 -0300 Subject: [PATCH 1/5] Create README.md --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 README.md diff --git a/README.md b/README.md new file mode 100644 index 000000000..d7015bf9d --- /dev/null +++ b/README.md @@ -0,0 +1,8 @@ +gitfiti +======= +gitfiti is a tool I wrote to blatantly abuse your github account's commit history calendar. + +I _highly_ recommend that you create a _new_ github repo when using gitfiti. + +Todo: +Finish web interface From 63cdc1110cec3476021f7e3ea25569a44f74b783 Mon Sep 17 00:00:00 2001 From: Eric Date: Tue, 30 Apr 2013 01:06:52 -0300 Subject: [PATCH 2/5] Update README.md --- README.md | 28 ++++++++++++++++++++++------ 1 file changed, 22 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index d7015bf9d..42bb30bc2 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,24 @@ -gitfiti -======= -gitfiti is a tool I wrote to blatantly abuse your github account's commit history calendar. +##gitfiti +gitfiti is a tool I wrote to (blatantly) abuse your github account's commit history calendar. -I _highly_ recommend that you create a _new_ github repo when using gitfiti. +I highly recommend that you create a _new_ github repo when using gitfiti. -Todo: -Finish web interface +###Usage: +1. create a new github repo to store your handiwork. +2. Run `gitfiti.py` and follow the prompts for username, art selection, offset, and repo name. +3. Run the generated `gitfiti.sh` from your home directory (or any non-git tracked dir) and watch it go to work. +4. Wait... Seriously, you'll probably need to wait a day or two for the gitfiti to show in your commit graph. + + +###Removal: +Fortunately if you regret your gitfiti in the morning, removing it is fairly easy: delete the repo you created for your gitfiti. + + +--- +####Todo: +- Remove 'requests' dependency +- Web interface +- Load "art" from a file +- Load commit content from a file +- ... +- Profit? From 8c62871c55cbfe114a669cb65078cb3540b477eb Mon Sep 17 00:00:00 2001 From: Eric Date: Tue, 30 Apr 2013 01:26:02 -0300 Subject: [PATCH 3/5] Update README.md --- README.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 42bb30bc2..cb7192672 100644 --- a/README.md +++ b/README.md @@ -9,10 +9,8 @@ I highly recommend that you create a _new_ github repo when using gitfiti. 3. Run the generated `gitfiti.sh` from your home directory (or any non-git tracked dir) and watch it go to work. 4. Wait... Seriously, you'll probably need to wait a day or two for the gitfiti to show in your commit graph. - ###Removal: -Fortunately if you regret your gitfiti in the morning, removing it is fairly easy: delete the repo you created for your gitfiti. - +Fortunately if you regret your gitfiti in the morning, removing it is fairly easy: delete the repo you created for your gitfiti (and wait). --- ####Todo: @@ -22,3 +20,9 @@ Fortunately if you regret your gitfiti in the morning, removing it is fairly eas - Load commit content from a file - ... - Profit? + + + + + +![alt text](http://f.cl.ly/items/0J463J0K1N020S1Q3E3l/er-small.png "tiny logo") From ded8c6d3475658053c490c9400421d65e1b7de24 Mon Sep 17 00:00:00 2001 From: Eric Date: Tue, 30 Apr 2013 14:00:18 -0300 Subject: [PATCH 4/5] Update README.md --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index cb7192672..5f45c472d 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,11 @@ -##gitfiti -gitfiti is a tool I wrote to (blatantly) abuse your github account's commit history calendar. +gitfiti _noun_ : carefully crafted griffiti in a github commit history calendar. + +`gitfiti.py` is a tool I wrote to (blatantly) abuse your github account's commit history calendar. I highly recommend that you create a _new_ github repo when using gitfiti. ###Usage: -1. create a new github repo to store your handiwork. +1. Create a new github repo to store your handiwork. 2. Run `gitfiti.py` and follow the prompts for username, art selection, offset, and repo name. 3. Run the generated `gitfiti.sh` from your home directory (or any non-git tracked dir) and watch it go to work. 4. Wait... Seriously, you'll probably need to wait a day or two for the gitfiti to show in your commit graph. From 5544b158d650e4fd24a43c8053a90f89a35e999d Mon Sep 17 00:00:00 2001 From: Eric Date: Tue, 30 Apr 2013 14:02:05 -0300 Subject: [PATCH 5/5] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 5f45c472d..14e5e652e 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ -gitfiti _noun_ : carefully crafted griffiti in a github commit history calendar. +gitfiti _noun_ : carefully crafted graffiti in a github commit history calendar. -`gitfiti.py` is a tool I wrote to (blatantly) abuse your github account's commit history calendar. +`gitfiti.py` is a tool I wrote to decorate your github account's commit history calendar by (blatantly) abusing git. I highly recommend that you create a _new_ github repo when using gitfiti.