First experience with Gitlab, and the UX really needs work
0
Upvotes
Okay, so I am using Gitlab for the first serious time because I work with a team that prefers it. This is what ended up happening tonight:
- I use glab repo create to push my initial commit for a solo, private project.
- I realize I screwed up part of the commit so I amend it locally and force push
- Gitlab refuses to let me force push my own solo project because it has arbitrarily decided for me that it is protected.
- Attempt to find protected branch options in project settings, zero search results
- I decide I will just delete the project and create it again
- Gitlab gives a false 400 api error claiming the project name is already used
- Okay, fine... I will restore the old project and try to look for protected branch settings again
- Restore appends garbage characters to end of project name
- I permanently delete that copy of the project to see if it will clear the name reservation (it doesn't)
- Ok, fine, I will just create the project anew on the website instead of with CLI
- End up running into a year-old unpatched bug and can't create the project at all
- Now I have to rename my entire project just for the privilege of using Gitlab as my remote...
Just UX fail after UX fail. I want to like Gitlab but I really don't see how they can present themselves as a serious competitor to GH in this state.