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
{{ message }}
This repository has been archived by the owner on Jun 30, 2022. It is now read-only.
I am adding lita as a bot to our whole org but I want to be able to restrict access to some critical plugins (github or CodeDeploy integrations) to the engineers.
Currently I believe I need to fork these gems to restrict the routes to the right Lita group. Or is there a way to do this at a global level that I missed.
If this does not exist I'll take a jab at a PR for this.
The text was updated successfully, but these errors were encountered:
Hmmm, turns out route class methods are being called before the config for the handler is initialized, making it pretty hard currently to extend this. Ideas welcome 👍
I am adding lita as a bot to our whole org but I want to be able to restrict access to some critical plugins (github or CodeDeploy integrations) to the engineers.
Currently I believe I need to fork these gems to restrict the routes to the right Lita group. Or is there a way to do this at a global level that I missed.
If this does not exist I'll take a jab at a PR for this.
The text was updated successfully, but these errors were encountered: