I can see there’s a chat section in my user settings on gitlab.com, but it just says I don’t have any active chat names. Is there something I can do about it? I’ve read about Mattermost integration in your blog posts, and it should be like Slack, which I believe is an online chat service. Can I use such a service via my private repository on gitlab.com? I’m looking for an easier team communication method than e-mail for short messages.
Can you be more specific about what you are looking for when it comes to chat? It sounds like you want an integration with your Project and a communication platform for general discussion on the project - correct me if I’m wrong here, however.
There are many chat integrations that work with GitLab right out of the box - with the most talked about being Slack as a lot of dev teams are using that anyway. With the Slack / GitLab integration you can have messages post to a certain channel based on certain events.
If you’re looking for something a bit deeper, I would continue looking into Mattermost, which it seems like you have familiarity with already: https://about.gitlab.com/2015/08/18/gitlab-loves-mattermost/
Looking forward to hearing more about your project and your needs?
As I understand it, Mattermost is included in GitLab. Where can I find it and how can I use it? That’s my question. I cannot see any trace of that anywhere, at least on gitlab.com (not on-premises).
Here is a pretty robust guide from the docs - let me know if it doesn’t apply to your situation and we can look some more:
Ehm, no, that doesn’t apply to my situation.
What are the exact words that I can tell you to make clear that I’m not talking about my local GitLab installation, but about the one hosted/cloud installation on gitlab.com? (And by “gitlab.com” I mean the web domain as the identity of the site.)
I think he might be talking about what’s here:
Yeah, nobody seems to be aware that there’s a hosted service on gitlab.com.
IIRC I’ve learned elsewhere that Mattermost is not available on gitlab.com and can only be integrated in local installations. Then it’s probably a deployment bug that the option is visible here. But I haven’t looked into it anymore since then.