Chapter 11 of 14

GitHub

A read-only link. Fygurs reads the milestones and issues of the repositories you name; a milestone attached to an initiative gives it its real progress and its real date, next to the planned one.

In this chapter

Connect

  1. On GitHub, create a fine-grained token: Settings, Developer settings, Personal access tokens, Fine-grained tokens. Choose the repositories to read, and under Repository permissions grant Issues read-only (Metadata read-only is added by itself). If the repositories belong to an organisation, choose it as the token's owner.
  2. In Fygurs, Settings › Integrations › GitHub. Paste the Access token, list the Repositories one per line as organisation/repository, then Connect. The token is encrypted and never shown again. A first read starts at once.
  3. Read GitHub now rereads the repositories when you want: "n milestones and m issues read". Reading only happens on demand.
The GitHub setting
The connection, the last read, and the milestones with their initiative.

Attach the milestones

The Milestones table lists each milestone with its repository, its due date (or "closed"), its open and closed issues, and an Initiative menu. Attach each milestone to the initiative it delivers: its issues follow. When a title matches, a link offers Attach to "…". Several milestones can serve the same initiative.

For a milestone that has no initiative yet, the same menu offers Create the initiative from this milestone: it takes the milestone's title, its description, its due date as the end date, Now and In progress if it is open, Done if it is closed, and it is attached at once. Nothing is created on reading: a milestone is a delivery unit, and you decide, milestone by milestone.

On the initiative

The GitHub block on an initiative's page shows "n of m issues closed" with a bar, the planned date against the date GitHub says (the latest due date among the attached milestones), and the drift: "n days past the planned date" in red, "before", or "on the planned date". Up to eight issues are listed, then "and n more".

  • In the initiatives list, the end date is followed by the GitHub date, red if later, green if earlier.
  • On the home page, Replan picks up the drifts GitHub announces.
  • In the business case, delivery takes the milestone's date, and a delay announced by GitHub puts a figure on the gain pushed back.
  • Change the token or the repositories reopens the form. Disconnect erases the token and everything read, and detaches the milestones.