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
fa16620d
Commit
fa16620d
authored
May 08, 2020
by
Ben Bodenmiller
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix bullet formatting on Projects API docs
parent
e034a781
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
4 deletions
+0
-4
doc/api/projects.md
doc/api/projects.md
+0
-4
No files found.
doc/api/projects.md
View file @
fa16620d
...
...
@@ -9,10 +9,8 @@ Values for the project visibility level are:
-
`private`
:
Project access must be granted explicitly for each user.
-
`internal`
:
The project can be cloned by any logged in user.
-
`public`
:
The project can be accessed without any authentication.
...
...
@@ -22,11 +20,9 @@ There are currently three options for `merge_method` to choose from:
-
`merge`
:
A merge commit is created for every merge, and merging is allowed as long as there are no conflicts.
-
`rebase_merge`
:
A merge commit is created for every merge, but merging is only allowed if fast-forward merge is possible.
This way you could make sure that if this merge request would build, after merging to target branch it would also build.
-
`ff`
:
No merge commits are created and all merges are fast-forwarded, which means that merging is only allowed if the branch could be fast-forwarded.
...
...
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