Heya,

Please forgive my ignorance on this subject. I do not have prior
experience with GitHub APIs or the various flavors of accounts. I'm
attempting to make use of Yetus against an installation of GitHub
enterprise. I'd like to use pre-commit/test-patch from Pull Requests. My
admins are strongly encouraging me toward GitHub's internal identity
management system -- either a GitHub App or an OAuth App. The GitHub
enterprise docs for my version are encouraging me away from the OAuth App
type.

In either case, it seems that access tokens are short-lived -- up to 10
minutes? Larger projects have test suites that can take hours. Yetus
accepts authentication credentials as part of process launch, and it
appears that these credentials remain static for the lifetime of the
process. For such a long test cycle, this won't work.

So, err, what am I missing? Or, how am I to manage delivering and renewing
credentials with Yetus?

Thanks,
Nick

Reply via email to