Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #2925

Closed
Open
Created Feb 06, 2013 by Administrator@rootOwner

Non-blocking project creation (why do we need to init the repo?)

Created by: rcarmo

Right now the way Gitlab works means that people who want/need a separate issue tracker or wiki need to initialize a repo, which is not practical - and, more to the point, you cannot even add people to a project until the repo is initialized, which also breaks the flow of setting up a team.

This can be done in a number of different ways (you can even go all the way and allow admins to predefine a "skeleton" repo to be cloned onto the new project), but the simplest way would probably be to set up a default README.md (which would init the repo) containing the setup instructions.

Assignee
Assign to
Time tracking