How do I know what my Github App will need to do? #127465
Unanswered
Wicaeed
asked this question in
Programming Help
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Body
I've been assisting our QE team with setting up some Github Actions that can trigger workflows in a centralized repo containing Playwright automation tests from another repository. We were able to get things working after setting up a fine-grained PAT with the appropriate Repository permissions that is owned by the Developer. This works for testing, but it's not really a scalable solution since we have several hundred repositories that would potentially be needing similar fine-grained PAT's created & approved.
My thoughts right now is instead of having many PAT's out there, we could instead have a Github App, and to store the App token as an Org-wide secret available for any repos to use as a way to trigger jobs in this centralized testing repo.
I'm not that experienced with Github Apps; What would my Github App code actually need to do in this instance?
Say the Github Action workflow file in my calling repo looks like this:
Would my Github App basically need to be doing exactly what is in the workflow file, but as API calls against Github API's?
Could the Github App itself handle rotating the token every 7 days, if we wanted it to?
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions