Preface
Currently, we copy and paste GitHub issue names + issue number into Google Sheets
We don’t want to leave tt-app, go to Github, find our issue,
then come back to tt-app to complete our entry
It would be neat to see all active issues, assigned to me. When creating my entry for the day.
I checked out Github’s REST API’s which are powered by something called octokit
https://docs.github.com/en/rest/issues/issues
Hurdles:
-
I needed to manually input a GitHub token I generated
Would we want new users to do this? Probably not
Octokit has a auth flow found here: https://docs.github.com/en/rest/guides/basics-of-authentication
-
What type would we add this new ‘array of issues’ to?
Quick answer is to slap it on the Person type
-
When / Where would be the best place to display the issues on the front end?
Quick answer, when making an ‘Entry’.
Preface
Currently, we copy and paste GitHub issue names + issue number into Google Sheets
We don’t want to leave
tt-app, go to Github, find our issue,then come back to
tt-appto complete our entryIt would be neat to see all active issues, assigned to me. When creating my entry for the day.
I checked out Github’s REST API’s which are powered by something called octokit
https://docs.github.com/en/rest/issues/issues
Hurdles:
I needed to manually input a GitHub token I generated
Would we want new users to do this? Probably not
Octokit has a auth flow found here: https://docs.github.com/en/rest/guides/basics-of-authentication
What type would we add this new ‘array of issues’ to?
Quick answer is to slap it on the Person type
When / Where would be the best place to display the issues on the front end?
Quick answer, when making an ‘Entry’.