![]() doc/ci/quick_start/README: improve sentence about link to a Lint tool ## What does this MR do? It improves the `doc/ci/quick_start/README.md` documentation. ## Are there points in the code the reviewer needs to double check? The reviewer can check that there is no more **CI settings** menu and that the Lint tool can be accessed under **Pipelines > Pipelines** and **Pipelines > Builds**. ## Why was this MR needed? Because the CI quick start documentation was not correct. ## Screenshots (if relevant) ## Does this MR meet the acceptance criteria? It is not a code change so I don't think the below criteria are relevant. - [ ] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [ ] API support added - Tests - [ ] Added for this feature/bug - [ ] All builds are passing - [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html) - [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [ ] Branch has no merge conflicts with `master` (if you do - rebase it please) - [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) ## What are the relevant issue numbers? I didn't check if there was an issue for this. See merge request !6301 |
||
---|---|---|
.. | ||
api | ||
build_artifacts | ||
docker | ||
examples | ||
img | ||
permissions | ||
quick_start | ||
runners | ||
services | ||
ssh_keys | ||
triggers | ||
variables | ||
yaml | ||
README.md | ||
enable_or_disable_ci.md | ||
environments.md | ||
pipelines.md |
README.md
GitLab CI Documentation
CI User documentation
- Get started with GitLab CI
- CI examples for various languages
- Learn how to enable or disable GitLab CI
- Pipelines and builds
- Environments and deployments
- Learn how
.gitlab-ci.yml
works - Configure a Runner, the application that runs your builds
- Use Docker images with GitLab Runner
- Use CI to build Docker images
- Use variables in your
.gitlab-ci.yml
- Use SSH keys in your build environment
- Trigger builds through the API
- Build artifacts
- User permissions
- API
- CI services (linked docker containers)