![](http://www.pocketworks.co.uk/images/logo.png)

# Git2Pdf

**Print physical Kanban cards from your GitHub issues, and stick that sweet stuff on your office wall**

## Install

    gem install git2pdf

## Use

### Single Repo

    # E.g. for this repo: https://github.com/uranusjr/macdown/issues
    $ git2pdf gen uranusjr/macdown -u tobinharris -p
    $ open issues.pdf

![](https://agilesurface-production.s3.amazonaws.com/images/3a0a74ed696fe6fddb3a9b7a9d84d03f)

### More repos

    $ git2pdf gen "uranusjr/macdown, pocketworks/git2rb" -u tobinharris -p
    $ open issues.pdf

### Alternative 1

    $ git2pdf gen -u tobinharris -p xxx -r "my-project, come-cool-repo, another-repo" -o my-organisation
    $ open issues.pdf

### Alternative 2

    $ git2pdf gen -u tobinharris -p xxx -r "pocketworks/my-project, pocketworks/come-cool-repo, pocketworks/another-repo"

TODO:

* Improve CLI syntax, it's a bit shite

## Features

* Generates a PDF of GitHub issues, so you can print them out and stick em' on your kanban board or scrum board or whatever.
* Include multiple repositories
*

# What's our workflow?

* We have a physical kanban board
* We get bored of duplicating your effort writing on index cards or post-it notes
* We manage all our features, business analysis, requirements and bugs in Github issues
* We tag our issues with a _class of service_ such as Bug, Feature, Task.
* We use waffle.io for different swim lanes on Github, and mirror these on our physical card wall
* Every Monday we print out our cards to `issues.pdf`
* We open it in Mac Finder, hit Cmd-Shift-2 to bring up the thumbs. Then select and delete any cards we've already printed, or that we don't want on the wall right now
* We chose print, A4, select 9 pages per sheet, and landscape
* We print it, grab some scissors, chop up the pages, and pin the cards on the wall
* Bosh!

## Contributing to github_issue_printer

* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.
* Fork the project.
* Start a feature/bugfix branch.
* Commit and push until you are happy with your contribution.
* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

## Copyright

Copyright (c) 2014 Tobin Harris. See LICENSE.txt for
further details.