452 uses a bot account, @ecoscope-elebot, to do recompiles.
The more robust way of managing this is with a GitHub App.
That is a lot of effort though (I've estimated at least duration:13, but up to duration:21), and involves managing an actual deployed service (so touches devops concerns).
At some scale of complexity, the effort/cost of doing a GitHub App is worth it, but probably not until we need to support recompiles for a medium-ish number of custom workflows repositories. (So long as we are managing most/all of the workflow repos ourselves, this is probably not worth the effort.)
452 uses a bot account, @ecoscope-elebot, to do recompiles.
The more robust way of managing this is with a GitHub App.
That is a lot of effort though (I've estimated at least
duration:13, but up toduration:21), and involves managing an actual deployed service (so touches devops concerns).At some scale of complexity, the effort/cost of doing a GitHub App is worth it, but probably not until we need to support recompiles for a medium-ish number of custom workflows repositories. (So long as we are managing most/all of the workflow repos ourselves, this is probably not worth the effort.)