4 ms·
This is a pathetic policy, Gitlab. For this reason alone, I'll stick to GitHub. What if I'm hospitalized or away on an extended trip? You just going to let som
by jonnyrockit 6y ago
This is a pathetic policy, Gitlab. For this reason alone, I'll stick to GitHub.
What if I'm hospitalized or away on an extended trip? You just going to let someone else take my account username?
No thanks.
- emilycook 6y agoI wouldn't worry about that, we have clear conditions that need to be met before we release a username [1]. It's meant to prevent name-squatting, not take usernames away from actual users. Although I do want to point out that GitHub also has this [2], it's just worded differently and doesn't outline what they consider "inactive". [1] https://about.gitlab.com/support/#dormant-namespace-requests https://about.gitlab.com/support/#dormant-namespace-requests [2] https://docs.github.com/en/github/site-policy/github-username-policy https://docs.github.com/en/github/site-policy/github-usernam...
- anonymoushn 6y agoWhat's an "active project"? OP says they discovered that their account had been renamed by having their workflow break. What kind of activity was OP regularly engaging in that depended on OP's account existing with the original name but did not flag OP's account as active?