:octocat: "Serverless" Kanban for GitHub Issues using gh-pages
Why waste time and money paying for a Ticket Tracker when you already work in GitHub? Now, you don't have to.
Multiple Repositories in an organization can be shown on a board (from different organizations too!). The repository is shown in gray next to the Issue number.
orgName/RepoName#123to the Issue or Pull Request body and linked Issues will show up with the column they are in, both below the Card and in the preview popup.
By clicking the :pencil2: icon next to the card title, multiple people can edit the Issue Body at once (ie in a meeting), and when editing is done, one person clicks Save to GitHub.
When doing Milestone (or Sprint) planning there is a view to easily move cards into milestones
Cards can be dragged from one column to the next
By using the
- [ ]notation in the body of an Issue or Pull Request, the progress of an Issue is shown in the top-right corner of a Card.
Shows a burnup chart for a Milestone (ie "Sprint" or "Iteration"). If you use select multiple repositories it will include all of them.
It also skips when nothing was opened or closed that day/month/year (useful to see weekends or holidays).
If an Issue or Pull Request contains an image then it will be shown in the Issue
Sometimes Pull Requests go to a branch other than the main branch. This makes it clear when that happens.
If you need to rename a column or remove a duplicate label you can get to this page from the Settings dropdown next to the filter link.
Plus, it comes with totally useful easter eggs you can unlock!
Just specify a GitHub repository in the URL and off you go!
npm startto start up the dev server and go to
npm run buildto generate the JS and CSS files in
# - Column Title)
gh-boarduses eTags provided by GitHub and saves them in
gh-pages(to trigger GitHub to start hosting the files)
npm run deploy
git pull https://github.com/philschatz/gh-board.git master
npm run deploy