Cheatography
https://cheatography.com
Special GitLab References
@user_name |
specific user |
@group_name |
specific group |
@all |
entire team |
#123 |
issue |
!123 |
merge request |
$123 |
snippet |
~123 |
label by ID |
~bug |
one-word label by name |
~"feature request| |
multi-word label by name |
9ba12248 |
specific commit |
9ba12248...b19a04f5 |
commit range comparison |
|
repository file references |
Cross-Project GitLab References
namespace/project#123 |
issue |
namespace/project!123 |
merge request |
namespace/project@9ba12248 |
specific commit |
namespace/project@9ba12248...b19a04f5 |
commit range comparison |
|
|
Headers
# |
H1 |
## |
H2 |
### |
H3 |
#### |
H4 |
##### |
H5 |
###### |
H6 |
Emphasis
*italic* |
italic |
*bold* |
bold |
~strikethrough~ |
strikethrough
|
`code` |
|
Images
Reference #1 |
|
Reference #2 |
 |
List
Lists
1. First ordered list item
2. Another item
* Unordered sub-list.
1. Actual numbers doesn't matter, just that it's a number
1. Ordered sub-list
4. And another item.
* Unordered list can use asterisks
- Or minuses
+ Or pluses |
|
|
Quotes
> Blockquotes are very handy in email to emulate reply text.
> This line is part of the same quote.
Quote break.
> This is a very long line that will still be quoted properly when it wraps. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. Oh, you can put Markdown into a blockquote. |
Links
Links
There are two ways to create links, inline-style and reference-style.
* inline link
* [reference link][Arbitrary reference text]
* relative reference to a repo file
* [numbers for reference link definitions][1]
* leave it empty [link text itself][] |
Tables
| header1 | header2 |
| ------- | ------- |
| cell1 | cell2 |
| cell3 | cell4 |
| Left Aligned | Centered | Right Aligned |
| :---------- | :------: | -----------: |
| Cell1 | Cell2 | Cell3 | |
|
Created By
Metadata
Favourited By
Comments
No comments yet. Add yours below!
Add a Comment
Related Cheat Sheets