-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Github Integration #38
Comments
Might also be nice to use Ketting with this =) it should work with their auth flows. |
On a different note, once we implement more of this I would think each time-tracker 'project' can be associated with 0 or more github repos |
Yea, it would make sense to have a or how about something like a 'public url' used in Storysuite? as someone aforementioned, Github would be very developer-centric. |
Yeah a list of urls would be dope =) |
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 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’.
The text was updated successfully, but these errors were encountered: