Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Inactive workflows


The following response channel workflows are marked as inactive, as we either do not yet have a process in place or the capacity to effectively address support questions, mentions or comments there. The ultimate goal is to


mentions-of-gitlab Slack channel

The #mentions-of-gitlab chat channel tracks mentions of GitLab across multiple sources. This allows us to respond to user requests across various platforms.

We currently track the following sources for GitLab mentions:

  1. Product Hunt
  2. Hacker News
  3. Reddit
  4. YouTube
  5. Quora

These mentions are piped by

All comments on our blog posts and any mention of GitLab on Lobsters also gets funneled to this channel using Zapier.


Respond to mentions of GitLab on Reddit, especially ones in the GitLab Subreddit.


Repond to comments made on the GitLab Youtube Channel.


Respond to questions about GitLab on Quora, especially the ones that appear in the GitLab Topic channel.

#movingtogitlab initiative

We have a daily reminder in the #community-alerts Slack channel to check for new #movingtogitlab tweets. This is done through TweetDeck, and the goal is to keep the #movingtogitlab trend and hashtag alive by retweeting appropriate tweets from our movingtogitlab Twitter account.

When you retweet every relevant post, leave a checkmark on the reminder, so the rest of the team knows that it's done.

Docs comments

These questions tend to be the most technical ones; consider involving experts when responding to them. Every comment should be answered.

Consider deleting the ones that aren't related to the documentation feedback. This kind of comments are distracting and aren't helpful to other users.

Types of comments that should be deleted:

Warning: If done poorly, it can cause more damage than good. Please consider these steps:

  1. Respond to the user (he gets an email with your response):
    • Sample response
  It looks like this issue is beyond the scope of the documentation comments. Please consider using <a href="">our community forum</a>, or see <a href="">other ways to get help</a>.
  Read more on how we handle documentation comments <a href="/handbook/marketing/community-relations/community-advocacy/#docs-comments">in our handbook</a>.
  Thanks for using GitLab!
  1. Make sure the response contains a link to our documentation process
  2. Delete the comment

Mailing List

Respond to questions on the GitLab Mailing List.

GitLab Forum

Questions from the GitLab Forum flow into ZenDesk, but can only be responded to from within the Forum environment.

Stack Overflow

The Stack Overflow tagged questions that relate to GitLab flow into Zendesk, but can only be responded to from within Stack Overflow.

After you create an account on Stack Overflow (if you don't already have one), you should start by answering a few simple questions in an area you're familiar with (a language, web framework, development platform, API, etc.) or in the GitLab tag(s) if you feel comfortable. The goal is to get enough "Reputation" and have access to a few more features.

Consider offering some of your Reputation using bounties if a question is particularly advanced and you don't believe you can answer yourself, and the question seems deserving of an answer (e.g. if it has lots of upvotes).

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license