←back to thread

Gitlab has introduced a five-user limit for free groups

(docs.gitlab.com)
160 points MattIPv4 | 1 comments | 20 Jun 23 17:14 UTC | HN request time: 0s | source
Show context
MattIPv4 ◴[20 Jun 23 17:15 UTC] No.36407258[source]▶
Just got an email from GitLab about a group I'm part of that has more than five users. The docs linked says "For existing namespaces, this limit is being rolled out gradually. Impacted users are notified in GitLab.com at least 60 days before the limit is applied.", however upon checking the group in GitLab, we are greeted by a big red box stating "Your top-level group [group] is over the 5 user limit and has been placed in a read-only state."
replies(4): >>36407685 #>>36407960 #>>36412533 #>>36416282 #
john_cogs ◴[20 Jun 23 18:00 UTC] No.36407960[source]▶
GitLab team member here.

The gradual roll out of this change started with a blog post[0] and included in-app notifications for the owners of impacted groups on GitLab.com.

If the group owner did not log in during the in-app notification period, they were then emailed (the email you received today) notifying that the group was impacted.

[0] - https://about.gitlab.com/blog/2022/03/24/efficient-free-tier...

replies(6): >>36408105 #>>36408731 #>>36409017 #>>36409044 #>>36410493 #>>36410877 #
1. faangsticle ◴[20 Jun 23 21:26 UTC] No.36410877[source]▶
“But the plans were on display…”

“On display? I eventually had to go down to the cellar to find them.”

“That’s the display department.”

“With a flashlight.”

“Ah, well, the lights had probably gone.”

“So had the stairs.”

“But look, you found the notice, didn’t you?”

“Yes,” said Arthur, “yes I did. It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard.”