Help us learn about your current experience with the documentation.
Take the survey.
Documentation and UI link testsFor testing:
haml-lint
, eslint
, and rubocop
.To run the relative link test locally, you can either:
To check the links on a single project:
lychee --offline --include-fragments <doc_directory>
where <doc_directory>
it the directory that contains documentation to check. For example: lychee --offline --include-fragments doc
.To check links on the entire GitLab documentation site:
docs-gitlab-com
clone. You can run make clone-docs-projects
to clone any projects you don’t have in that location.docs-gitlab-com
directory.hugo
, which builds the GitLab Docs site.lychee --offline public
to check links.To test documentation links from GitLab code files locally, you can run
eslint
: For frontend (.js
and .vue
) files.rubocop
: For .rb
and .haml
files.eslint
tests
Open the gitlab
directory in a terminal window.
Run:
scripts/frontend/lint_docs_links.mjs
If you receive an error the first time you run this test, run yarn install
, which installs the dependencies for GitLab, and try again.
rubocop
tests
Open the gitlab
directory in a terminal window.
To run the check on all Ruby files:
rubocop --only Gitlab/DocumentationLinks/Link
To run the check on a single Ruby file:
rubocop --only Gitlab/DocumentationLinks/Link path/to/ruby/file.rb
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4