
This account is no longer used. Please tweet at @GitLab for help.
Joined November 2015
- Tweets535
- Following1
- Followers1.1K
- Likes2
This account is no longer used to respond to support requests, please direct questions to @GitLab instead.
Replying to @devplusbe
we had some issues with our Sidekiq workers getting stuck, is everything working again?
Replying to @potasiyam
Sorry about the downtime, is everything working now?
Replying to @purwandi_m
That was a custom Slack command api.slack.com/slash-commands…
it would be part of the 10GB/project. The file stays part of the repository, like normal, Git just indexes it differently.
Replying to @atmosx0 @patmatzidis
sorry for the slow response and thanks for the advice. I think the frontend team might have already fixed it.
Replying to @samuelmesq
sorry for the embarrassing response time to your tweet. It should be running fine for you now
Replying to @joubertredrat
Hi, We’ve updated the issue, looks like it’s resolved now.
Replying to @tgi74
Sorry to hear you are having problems. What link exactly are you clicking on?
Replying to @bgondy
the setting is global, so to achieve this you would need to change it every time you create a new project. docs.gitlab.com/ce/administr…
Replying to @VimKanzo
Is your GitLab instance running ? Please try running sudo gitlab-ctl status command and check if your instance is running or not
Replying to @rostendorf
An MR to fix this was submitted and will be released on our latest 8.10.1 release. See, gitlab.com/gitlab-com/suppor…
Replying to @abhijitghogre
This is a bug in 8.10 that will be fixed in 8.10.1. If you want a quick workaround, see gitlab.com/gitlab-org/gitlab…
Replying to @__sebastien
Are you still experiencing this issue while using Google Chrome?