I’m using rolling and trying to get commit-archive up to GitHub but the confounding factor is the fact that multiple people are going to be making changes to the firewall. So I don’t want to encode the username/password/ssh-key in the config because then it would look to GitHub like all the commits are coming from that user. Everyone logs in via RADIUS and right now I’ve just asked everyone pretty please make an ssh-key and add it to GitHub but there’s nothing I can do to enforce it if they don’t (which means we lose those changes in the commit archive).
My next idea was to make a GitHub App, add it to our organization, and… not sure what to do after that. I was thinking to use an “Installation Access Token” (Generating an installation access token for a GitHub App - GitHub Enterprise Server 3.16 Docs) probably renewed with a scheduled job, but I can’t figure out how to tell commit-archive to use that. Would it be easier to just use a commit hook instead of the builtin commit-archive configuration to provision access tokens and do custom git logic?