Click the orange Start Screen in the top left navigation to search for any Github repo you want to track with Blazemetrics.
The search results will display all relevant repos that match your search.
You can also scroll the left navigation to see all repos for which you are a collaborator.
Blaze connects to all your available Github repos via webhook.
Once connected, you will be able to track time, track budget and set due dates to any Github repo you own.
Milestones are a handy way to organize your projects by releases, sprints, due date or feature.
Blaze enhances standard Github Milestones by helping you track your time against a budget and due date.
Edit both existing Github Milestones or create new ones from within Blaze.
Blaze provides a great way to track, filter and report on Github Issues.
Click "Dashboard" in the left navigation to display the high level breakdown of what you've worked on by Github Issue type.
Drill down by clicking the "Issues" button in the left navigation to sort Issues by open, closed, author, label, milestone, assignee, newest or oldest.
Applying filters will update the 4 tiles displayed below by calculating total hours, overdue tasks, costs, and percentage of total budget.
Make sure to follow the configuration instructions before tracking any time to Blazemetrics.
Next, edit any file in your local repo and prepare to commit your change to Git.
When preparing your commit message, use the following format to assign time to a specific issue:
git commit -m 'fixes #1234 I(1234)'
In the above example,
fixes #1234 will close the issue, and adding
I(1234) will save the time spent working on the fix Github Issue #1234.
Note: You can also track time to a Milestone using the following format
git commit -m 'foo M(1)' where
M(1) is the number of the milestone.