GitHub Burndown Chart as a Service http://radekstepan.com/burnchart
Go to file
Radek Stepan 2cd2ce74e5 escaping a string for js; refs #19 2013-08-02 22:41:16 +01:00
public cleanup of the style 2012-05-25 17:03:43 +01:00
templates escaping a string for js; refs #19 2013-08-02 22:41:16 +01:00
.gitignore execute coffee, do not precompile 2012-05-25 18:59:32 +01:00
README.md Update README.md to include api_token for private repo support 2013-07-10 18:48:55 -07:00
app.coffee throw on request error 2013-07-16 20:33:42 +01:00
config.yml Add api_token for private repo support 2013-07-10 18:39:47 -07:00
example.png show issues closed on that day onhover, add y axis, close #2 2012-05-24 17:14:01 +01:00
package.json escaping a string for js; refs #19 2013-08-02 22:41:16 +01:00
start.js ukrainian and flatiron version of the app 2012-12-08 19:54:43 +00:00

README.md

GitHub Burndown App

An app that displays a burndown chart for your GitHub Issues.

image

Requirements:

You can install all the following dependencies by running:

$ npm install -d

Configure:

The app is configured by pointing to a GitHub user/project. Do so in config.yml:

github_user:    'intermine'
github_project: 'InterMine'
project_name:   'Core InterMine Project'

The project_name key-value pair represents the title of the burndown chart that you will see in the top right corner of the page.

To configure the app for a private GitHub project, you must additionally set the api_token key-value pair in config.yml:

api_token:      '5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8'

To generate an access token, see your GitHub Application Settings.

Milestones

Then visit your GitHub project's Issues page and create a new milestone with a date due in the future. This will represent your iteration. This app will pick the Milestone with the closest due date in the future as the current one.

Sizes

Then assign a few labels to tickets in this Milestone. These labels will represent your perceived size of the task. The label takes a form of size [number] so to say that an Issue is as big as 5 points I would create and assign this label (don't worry about the colors...):

size 5

Weekends

If you have days when you do not work on a project, edit the config.yml file with a list of days of the week when you are off. The numbers are 1 indexed and follow the international standard of starting a week on Monday, so for a Saturday and Sunday weekend do this:

weekend: [ 6, 7 ]

Base URL to app

If the app does not live in the root path of your server, edit the base_url property in the config file.

Use:

$ node start.js

Then visit http://127.0.0.1:3000/ or whichever port was configured in process.env.PORT.

The orange line - this represents you closing the Issues as you go through them. When you hover over it you will see, for each day, what the closed Issues were and how many points are left.

The blue line - this represents the dropping size of the outstanding Issues planned for the iteration/Milestone.

There is nothing to save in a database so each refresh of the page fetches all of the latest information from GitHub.

Enjoy!