Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
999efa05
Commit
999efa05
authored
Oct 19, 2020
by
Mike Jang
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'patch-250' into 'master'
Fixes to project.md See merge request gitlab-org/gitlab!44824
parents
87cc057a
34654478
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
10 deletions
+10
-10
doc/gitlab-basics/create-project.md
doc/gitlab-basics/create-project.md
+10
-10
No files found.
doc/gitlab-basics/create-project.md
View file @
999efa05
...
@@ -34,16 +34,16 @@ To create a new blank project on the **New project** page:
...
@@ -34,16 +34,16 @@ To create a new blank project on the **New project** page:
1.
On the
**Blank project**
tab, provide the following information:
1.
On the
**Blank project**
tab, provide the following information:
-
The name of your project in the
**Project name**
field. You can't use
-
The name of your project in the
**Project name**
field. You can't use
special characters, but you can use spaces, hyphens, underscores, or even
special characters, but you can use spaces, hyphens, underscores, or even
emoji. When adding the name, the
**Project slug**
will auto populate
.
emoji. When adding the name, the
**Project slug**
auto populates
.
The slug is what the GitLab instance
will use
as the URL path to the project.
The slug is what the GitLab instance
uses
as the URL path to the project.
If you want a different slug, input the project name first,
If you want a different slug, input the project name first,
then change the slug after.
then change the slug after.
-
The path to your project in the
**Project slug**
field. This is the URL
-
The path to your project in the
**Project slug**
field. This is the URL
path for your project that the GitLab instance
will use
. If the
path for your project that the GitLab instance
uses
. If the
**Project name**
is blank, it
will auto populate
when you fill in
**Project name**
is blank, it
auto populates
when you fill in
the
**Project slug**
.
the
**Project slug**
.
-
The
**Project description (optional)**
field enables you to enter a
-
The
**Project description (optional)**
field enables you to enter a
description for your project's dashboard, which
will help
others
description for your project's dashboard, which
helps
others
understand what your project is about. Though it's not required, it's a good
understand what your project is about. Though it's not required, it's a good
idea to fill this in.
idea to fill this in.
-
Changing the
**Visibility Level**
modifies the project's
-
Changing the
**Visibility Level**
modifies the project's
...
@@ -128,11 +128,11 @@ To use a custom project template on the **New project** page:
...
@@ -128,11 +128,11 @@ To use a custom project template on the **New project** page:
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/26388) in GitLab 10.5.
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/26388) in GitLab 10.5.
When you create a new repository locally, instead of
going to GitLab to manually
When you create a new repository locally, instead of
manually creating a new project in GitLab
create a new project and then
[
clone
the repository
](
start-using-git.md#clone-a-repository
)
and then
[
cloning
the repository
](
start-using-git.md#clone-a-repository
)
locally, you can directly push it to GitLab to create the new project, all without leaving
locally, you can directly push it to GitLab to create the new project, all without leaving
your terminal. If you have access rights to the associated namespace, GitLab
will
your terminal. If you have access rights to the associated namespace, GitLab
automatically create a new project under that GitLab namespace with its visibility
automatically create
s
a new project under that GitLab namespace with its visibility
set to Private by default (you can later change it in the
[
project's settings
](
../public_access/public_access.md#how-to-change-project-visibility
)
).
set to Private by default (you can later change it in the
[
project's settings
](
../public_access/public_access.md#how-to-change-project-visibility
)
).
This can be done by using either SSH or HTTPS:
This can be done by using either SSH or HTTPS:
...
@@ -145,7 +145,7 @@ git push --set-upstream git@gitlab.example.com:namespace/nonexistent-project.git
...
@@ -145,7 +145,7 @@ git push --set-upstream git@gitlab.example.com:namespace/nonexistent-project.git
git push
--set-upstream
https://gitlab.example.com/namespace/nonexistent-project.git master
git push
--set-upstream
https://gitlab.example.com/namespace/nonexistent-project.git master
```
```
Once the push finishes successfully, a remote message
will indicate
Once the push finishes successfully, a remote message
indicates
the command to set the remote and the URL to the new project:
the command to set the remote and the URL to the new project:
```
plaintext
```
plaintext
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment