Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Correct the spacing of unordered markdown lists
in docs, to maintain standards of documentation,
in /user and others.
|
|
|
|
Previously, we used brackets to denote the tier badges,
but this made Kramdown, the docs site Markdown renderer,
show many warnings when building the site. This is now
fixed by using parentheses instead of square brackets.
This was caused by [PREMIUM] looking like a link to
Kramdown, which couldn't find a URL there.
See:
- https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/484
- https://gitlab.com/gitlab-org/gitlab-ce/issues/63800
|
|
The original issue didn't specify this, but the code always allowed
reporters to do everything here. I think that's correct because
1. Developer permissions normally refer to code, and boards are to do
with issues.
2. Reporters can manage epics, as well as labels on
issues, which are in a similar space.
|
|
|
|
|
|
- Extract 445px as a variable
- Documentation changes: new image and update copy
|
|
|
|
Markdown renderers find it easier to determine
where lists start and end when lists are surrounded
by new lines.
For consistency, also ensure entries in the list
are aligned when they span multipls lines.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|