Stack at initializing new repo
Steps to reproduce:
- Owner creates new repo, adds another user as maintainer
- Maintainer has no clone button (thx to SO so I know that is an expected quirk of gitlab)
- Maintainer follows the default instructions
Push an existing folder
cd existing_folder
git init
git remote add origin git@gitlab.com:**/**.git
git add .
git commit -m "Initial commit"
$ git push origin master
remote: GitLab:
remote: A default branch (e.g. master) does not yet exist for **/**
remote: Ask a project Owner or Maintainer to create a default branch:
remote:
remote: https://gitlab.com/**/**/-/project_members
remote:
To git@gitlab.com:**/**.git
! [remote rejected] master -> master (pre-receive hook declined)
- End user (maintainer) is stuck unable to do anything, having to read several closed issues on gitlab to figure out he can't fix anything
Suggestion:
Instructions are misleading for anyone except owner. Non-owners should get a simple note that they have to ask owner to create a first commit. Clone button should exist for end users, they should be able to fork, create branch in fork and submit a PR to a new "virtual" branch.