You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was following the guidance of Working with GitHub Apps and had a general question. If I'm trying to work on setting up a GitHub App that acts on it's own behalf so that I can use it to read contents from public GitHub Repos, what do I need to do with regards to the requirements of working with an installation?
Right now, what works is I install the app to my personal GitHub account and then that allows me to read from any public GitHub repository, but I don't know if that goes against the spirit of creating an installation token (e.g. creating an installation token of the application for my personal github account and then using that to do nothing with my personal GitHub account). I wonder if there's a pattern that people take when they want to authenticate a GitHub App acting on it's own behalf to interact with public GitHub repositories and resources.
Right now, my primary reason for wanting to have an authenticated client here is to prevent hitting the throttling limits that can occur when running unauthenticated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I was following the guidance of Working with GitHub Apps and had a general question. If I'm trying to work on setting up a GitHub App that acts on it's own behalf so that I can use it to read contents from public GitHub Repos, what do I need to do with regards to the requirements of working with an installation?
Right now, what works is I install the app to my personal GitHub account and then that allows me to read from any public GitHub repository, but I don't know if that goes against the spirit of creating an installation token (e.g. creating an installation token of the application for my personal github account and then using that to do nothing with my personal GitHub account). I wonder if there's a pattern that people take when they want to authenticate a GitHub App acting on it's own behalf to interact with public GitHub repositories and resources.
Right now, my primary reason for wanting to have an authenticated client here is to prevent hitting the throttling limits that can occur when running unauthenticated.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions