You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within my organization, there are quick and easy processes for building and deploying Node.js apps using standard pipelines. Meanwhile, custom docker images and helm charts require significantly more overhead and approval.
I'm currently deploying an instance of repository-settings as a custom Node.js app, but I would like to migrate to using safe-settings instead. Currently, I would need to copy the repository to our internal Github Enterprise instance and maintain it manually, which is a poor security stance. If I could install it from NPM, I could keep it updated automatically.
Contribution
I would gladly offer to contribute a PR myself but, unfortunately, this fundamentally requires a maintainer. Still, I will gladly provide whatever assistance I can.
The text was updated successfully, but these errors were encountered:
Prerequisites:
N/A, not related to the GitHup API.
New Feature
I would like to see this published to the public NPM registry as a packaged probot module, similar to @repository-settings/app.
Reasoning
Within my organization, there are quick and easy processes for building and deploying Node.js apps using standard pipelines. Meanwhile, custom docker images and helm charts require significantly more overhead and approval.
I'm currently deploying an instance of repository-settings as a custom Node.js app, but I would like to migrate to using safe-settings instead. Currently, I would need to copy the repository to our internal Github Enterprise instance and maintain it manually, which is a poor security stance. If I could install it from NPM, I could keep it updated automatically.
Contribution
I would gladly offer to contribute a PR myself but, unfortunately, this fundamentally requires a maintainer. Still, I will gladly provide whatever assistance I can.
The text was updated successfully, but these errors were encountered: