Integrate GitHub API

[jack89roberts]

• Emojis for people's project preferences.
  • Specifically emojis for people who have capacity on projects that have demand.
• Flag projects that are confirmed but not on Forecast (and maybe auto-create them in Forecast).
• Sanity check project information on GitHub vs on Forecast in general (e.g. dates, FTE).
• Extract project descriptions for some future dashboard (e.g. for #22 #18 ).

[martintoreilly]

For the purposes of mapping Github to Forecast can we use the following:

Github project board column	Wimbledon status	Expected Forecast user
With funder	Unconfirmed	Unconfirmed
Finding resources	Confirmed	Resource required
Awaiting start	Confirmed	Named REG or Partner placeholder
Active	Confirmed	Named REG or Partner placeholder
Completion review	Confirmed	Named REG or Partner placeholder

The "Done" column on the Github project board may be a bit tricky, as some issues in that column will be ones that have passed through the stages above, whole others will be projects that never made it to "With funder" or didn't get funded or were duplicate issues for the same project. We could potentially use labels to distinguish those projects in "Done" that we should not have represented in Forecast.

It would be quite interesting to see what proportion of projects / FTE effort are temporarily on our forecast plan as unconfirmed, but do not make it to confirmed. However, I think this will be something for when we have the ability to store previous allocation plans in Wimbledon

[edwardchalstrey1]

Upon merge #43

On the web app home page, a preference/ availability table page can be accessed: /preferences (https://wimbledon-planner.azurewebsites.net/preferences)

This lists all the projects with at least some resource requirement, against the REG team members.

Each cell of the table shows the team member preference for the project and their FTE availability within the date range for which resources need to be allocated (expressed as the mean for that range).

Preference emojis are taken from the Hut23 issues using GitHub GraphQL API and will be retrieved from the issue itself (i.e. the top comment).

If no emojis are found then each comment on the issue will be searched until we find one with at least one emoji, then the emojis for that comment will be taken as preferences.

Team members without an emoji for an issue are represented with a question mark.

Issues with zero emojis are not included in the table.