-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
GitLab integration #6795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
That is what we are waiting for! I would like to outline our requirements for a good integration here. Besides the ability to embed issues, epics and merge requests from a selfhosted gitlab instance it would be beneficial when the embeds update automatically showing the current status like if an issue is open or closed, when was the last change etc. Because our instance is private only, outline would need an api key to fetch the information. Is this kind of integration planned? |
Yes @thedarkside agreed this is how it should work |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
It would be great to have this functionality. |
i concur it would be nice to have this |
In case one wanted to continue here from the community-side of things, should we also wait for this "solution to be pluggable" or might GitLab rather just be the next work item bringing with it the decoupling mentioned in the linked comment, also paving the way for Linear and sorts? |
Yep, not sure on the priority of GitLab support itself for the maintainer team, it's not requested all that often |
For us it is a priority and I would put in significant effort into porting any existing integration to GitLab, which is mostly copy and paste and reading the documentation about API endpoints. Will return here when the "pluggable solution" exists and can be adapted from. |
After #6406 similar to #4427
The text was updated successfully, but these errors were encountered: