| Age | Commit message (Collapse) | Author |
|---|
|
Clarify rules for code blocks, including spaces
above and below, and to use tilde when code blocks
contain triple backticks
|
|
Don't use go mod vendor
See merge request gitlab-org/gitlab-ce!31721
|
|
Allow to use focus: true in specs
See merge request gitlab-org/gitlab-ce!31691
|
|
|
|
Add missing (FREE ONLY) docs tier badge
See merge request gitlab-org/gitlab-ce!31755
|
|
Elasticsearch versioned schema for Snippet
See merge request gitlab-org/gitlab-ce!31465
|
|
Add BrowserStack details to Frontend Dev Guide
See merge request gitlab-org/gitlab-ce!31744
|
|
|
|
|
|
GitLab.com also has an up-to-date Postgres mirror.
|
|
- This provides users with an easy to apply gitmessage template
for ease of seeing the commit guidelines here when they commit
against gitlab: i
https://docs.gitlab.com/ee/development/contributing/merge_request_workflow.html#commit-messages-guidelines
|
|
Explain indentation more carefully, and expand examples
|
|
|
|
|
|
|
|
This change comes out of a discussion between Ben Kochie and me, around
this MR: https://gitlab.com/gitlab-org/gitlab-pages/merge_requests/164
gitlab-elasticsearch-indexer already uses `go mod` without a `vendor/`
directory. It has caused some intermittent build failures in the
gitlab-ce/ee CI pipelines, but has otherwise been fine. I think that
treating our Go dependencies in the same way we do our Ruby or Node.js
ones is reasonable, and it has some minor benefits:
* Contributors find it easier to submit MRs
* MRs are easier to review
* Makefiles are easier to write
|
|
|
|
Replace redirect_from with disqus_identifier in docs
See merge request gitlab-org/gitlab-ce!31595
|
|
|
|
Adds MD010 (Hard tabs), MD012 (blank lines), MD029 (ordered
list prefix), MD030 (spaces after list markers), and fixes
remaining docs that were failing these tests
|
|
- Add a new guideline regarding the file location of background
migrations
- Add a new section about execution timing guidelines for all different
kinds of migrations
|
|
Update Migration Style Guide. Remove MySQL mentions
See merge request gitlab-org/gitlab-ce!31531
|
|
The githost.log name was often confused with GitHost.io. Rename this to
git_json.log to make it clear it's coming from Git and that it's JSON
data.
|
|
Update proofreader.md
See merge request gitlab-org/gitlab-ce!26644
|
|
Let's use disqus_identifier since this is a more
descriptive name. We will need redirect_from for
another purpose anyway (Nanoc redirects).
|
|
|
|
|
|
Fix links as discovered by the lint in the docs project
|
|
|
|
|
|
MD002 - First header should be level 1
MD006 - Start bullets at beginning of line
MD019 - No multiple spaces after header style
MD022 - Headers surrounded by blank lines
MD025 - Only 1 level 1 header
MD028 - No blank lines within blockquote
MD038 - Spaces inside code span elements
|
|
|
|
Update end-to-end style guide doc with new guideline
See merge request gitlab-org/gitlab-ce!31342
|
|
* Remove PNGs in favor of dynamically rendered graphs
* Eliminate <b> styling because this is no longer supported
* Change <br /> to <br> because the latter is only supported
* Add quotes around subgraph titles
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
|
|
This will ultimately replace the stats.js that
exists in EE.
|
|
|
|
Many code blocks are 4spaced, and they render in GitLab
without coloring as a result, even though they are
fenced with a language label. If in a list, other items
will render as being in a code block too, even if not
meant to. This fixes all these issues for most docs in
/development, and cleans up other whitespace issues too
|
|
|
|
Add development documentation on label filtering
Closes #49651
See merge request gitlab-org/gitlab-ce!30741
|
|
Add points how to prepare for database reviews
Closes #65126
See merge request gitlab-org/gitlab-ce!31158
|
|
Following the single docs codebase change, all internal links
should be relative. Also cleans up one table
|
|
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/65126.
Came up in the database office hours call on 2019-07-25.
|
|
|
|
We have a fairly good guide to Code Reviews, but can be improved
by adding a few examples of what a good code review looks like
at GitLab, specifically ones where there is a bit of back and
forth, "nit-picking," etc. This would:
+ help set expectations of newly hired engineers around what our
process looks like when it is functioning what level of scrutiny
their code will be under
+ how we have technical conversations
+ show by example how after you're done crafting a solution, there
can still be extra work done either tidying up code and/or managing
the communication and conversations about your proposed MR
|
|
This topic comes up periodically, and we've investigated several options
for changing the way we filter labels. Unfortunately, we have yet to
find an option that is strictly better than the current state.
|
|
Add documentation on how to add dependencies to yarn
See merge request gitlab-org/gitlab-ce!31066
|
|
|
|
Some markdown headers needed tweaking to adhere
to standards, including blank lines above and below,
only one space after hash, first header should be
h1, and only one h1 per doc
|
