For interactions with GitHub (e.g., anything other than reading) I think it would be best to create a GitHub app for API interaction. We can create discussions, reply on issues (#28, etc.), and more.
Looking across the available packages, https://github.com/yanyongyu/githubkit seems like the best fit. It utilizes httpx, has Octokit-like levels of feature set, async support, and is kept up to date.
Basic Example
Create GitHub app
Process bot requests, interact with library inside of our project, send to GitHub, and vice versa
Listen to requests from GitHub through web server API calls/webhooks
Project layout could be tricky. Do we have a fourth segment (on top of src/{byte,web,database}) for the GitHub portion, or can we intermingle in the byte "domain"?
[!NOTE]
We utilize Polar.sh to engage in regular as well as pledge-based > sponsorship.
Summary
For interactions with GitHub (e.g., anything other than reading) I think it would be best to create a GitHub app for API interaction. We can create discussions, reply on issues (#28, etc.), and more.
Looking across the available packages, https://github.com/yanyongyu/githubkit seems like the best fit. It utilizes
httpx, has Octokit-like levels of feature set, async support, and is kept up to date.Basic Example
https://docs.github.com/en/apps/creating-github-apps/about-creating-github-apps/deciding-when-to-build-a-github-app
Drawbacks and Impact
No response
Unresolved questions
Project layout could be tricky. Do we have a fourth segment (on top of
src/{byte,web,database}) for the GitHub portion, or can we intermingle in thebyte"domain"?