Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
Developer Documentation
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
brienne
Developer Documentation
Commits
e1b32fc4
Commit
e1b32fc4
authored
7 years ago
by
Sean Madsen
Browse files
Options
Downloads
Patches
Plain Diff
Markdown - explain blank line before lists
parent
3737227a
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/documentation/markdown.md
+6
-1
6 additions, 1 deletion
docs/documentation/markdown.md
with
6 additions
and
1 deletion
docs/documentation/markdown.md
+
6
−
1
View file @
e1b32fc4
...
...
@@ -201,13 +201,18 @@ to this section in the future.
### Unordered lists
```
```
text
Here is my paragraph (with a blank line after).
* My first item is here.
* My second item is here and a
bit longer than the first.
* Then, a third.
```
!!! note
If you don't
**include a blank line before your first list item**
, then the list will become part of the previous element (paragraph, heading, etc).
Alternate syntax:
*
Unordered lists also recognize
`-`
and
`+`
as item delimiters.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment