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 Dec 11, 2021. It is now read-only.
The currently setup of GitLab Issue Bot (GLIB) requires each user to run their own instance of it.
But setup can be easier! If we make GLIB a hosted GitLab and Slack app, we can make distribution and setup a simple and easy process. Users wouldn't have to run their own instance.
Proposed Setup Flow
A user clicks Setupon the GLIB website.
GLIB redirects them to GitLab to login and give API access.
After logging in with GitLab, the user is redirected to a page to install the Slack app.
The user signs into Slack and adds the bot user.
The user goes to Slack and starts using GLIB!
The only thing that this setup doesn't cover is self hosted GitLab instances. That's a little more complex.
The currently setup of GitLab Issue Bot (GLIB) requires each user to run their own instance of it.
But setup can be easier! If we make GLIB a hosted GitLab and Slack app, we can make distribution and setup a simple and easy process. Users wouldn't have to run their own instance.
Proposed Setup Flow
Setup
on the GLIB website.The only thing that this setup doesn't cover is self hosted GitLab instances. That's a little more complex.
To-Do
Links / Ref
The text was updated successfully, but these errors were encountered: