Zeke Sikelianos
Zeke Sikelianos
cc @technillogue @joehoover @daanelson
Thanks for reporting. Cog's support for env/secrets at build time and run time is not yet well documented. Can you share a bit more detail about what you're trying to...
I see. Are you running Cog on your own infrastructure and wanting to be able to send webhooks?
> using "^8.0" throws the same error as present What is the error? Maybe it needs to be `^8.0.0`?
Trying to figure out why Glitch doesn't support all semver-compliant ranges: https://twitter.com/zeke/status/974723218064855040 TwitterZeke Sikelianos on Twitter“@_gw can you take a peek at this `engines.node` question? https://t.co/RJBmkCmgbK”
💡 What about storing encrypted values in `.github/config.yml` that only a probot installation can decrypt? Like [Travis Encryption keys](https://docs.travis-ci.com/user/encryption-keys/).
Hi @stale. Yeah this issue is still relevant.
GitHub Secrets are still only available in GitHub Actions, but not to GitHub Apps. cc @jovel
@gr2m suggested that there might currently be some roadblocks for such a bot: https://platform.github.community/t/repositories-which-have-protected-branches-with-push-restrictions-have-no-ability-to-grant-push-rights-to-integrations/1376
Hey @ocombe is that bot source public?