by radekstepan

radekstepan / burnchart

GitHub Burndown Chart as a Service

225 Stars 48 Forks Last release: over 2 years ago (v3.3.0) GNU Affero General Public License v3.0 438 Commits 5 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:


GitHub Burndown Chart as a Service. Answers the question "are my projects on track"?

Build Status Dependencies License



  1. Running from the browser, apart from GitHub account sign in which uses Firebase backend.
  2. Private repos; sign in with your GitHub account.
  3. Store projects in browser's
  4. Off days; specify which days of the week to leave out from ideal burndown progression line.
  5. Trend line; to see if you can make it to the deadline at this pace.
  6. Different point counting strategies; select from 1 issues = 1 point or read size from issue label.


$ npm install burnchart -g
$ burnchart --port 8080
# burnchart/3.0.0 started on port 8080


At the moment, there is no UI exposed to change the app settings. You have to either edit the

file or use URL query string parameters to override these on a per-user basis.

Config Fields

An array of days when we are not working where Monday = 1. The ideal progression line won't drop on these days.

"off_days": [ ]

Choose from

which means each issue is worth 1 point or
where issue labels determine its size.
"points": "ONE_SIZE"

If you specify

above, this is the place to set a regex used to parse a label and extract points size from it. When multiple matching size labels exist, their sum is taken.
"size_label": /^size (\d+)$/

You can also create your own app theme. Create a LESS file following the example of the default app theme, "monza", in

, include the file in
and finally specify the theme in the config:
"theme": "monza"

URL Query String

The main config file can be overriden by passing URL query string parameters. This allows app customization on a per-user basis. We use the qs library to parse and lodash to merge in the new values. The following example will switch off the main theme and set off days to fall on the weekend:



To run your local version of the app, install all the NPM dependencies, watch the source files in one window, and start the static file server in the other in

$ nvm use
$ npm install
$ make watch
$ make start-dev
# burnchart/3.0.0 (dev) started on port 8080

GitHub Pages

1. GitHub

To serve the app from GitHub Pages set the "Source branch" in the

page of your repository.

2. Firebase

Then, signup for Firebase and go to your console and create a new project there.

You can leave the Database/Storage section as is, you only want to configure your "Authentication". There, enable "GitHub" and add your domain in "Authorised domains". Mine is set to

type: Custom
. If you want to run the app locally, you may want to add
as well.

Since you are using your own Firebase project, you want to copy a couple of keys/ids into the

section of
  • firebase.apiKey
    is "Web API key" from the "Settings" page (in "Project Overview")
  • firebase.authDomain
    is one of the authorised domains in "Authentication", then "Sign-in method"

Sync with

To serve the app from GitHub Pages that are in sync with master branch, add these two lines to

, in the
[remote "origin"]
[remote "origin"]
  fetch = +refs/heads/*:refs/remotes/origin/*
  url = [email protected]:user/repo.git
  push = +refs/heads/master:refs/heads/gh-pages
  push = +refs/heads/master:refs/heads/master

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.