4b6fd0df62
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 |
||
|---|---|---|
| .. | ||
| administration | ||
| api | ||
| ci | ||
| container_registry | ||
| customization | ||
| development | ||
| downgrade_ee_to_ce | ||
| gitlab-basics | ||
| hooks | ||
| incoming_email | ||
| install | ||
| integration | ||
| intro | ||
| legal | ||
| logs | ||
| markdown | ||
| migrate_ci_to_ce | ||
| monitoring | ||
| operations | ||
| permissions | ||
| profile | ||
| project_services | ||
| public_access | ||
| raketasks | ||
| security | ||
| ssh | ||
| system_hooks | ||
| update | ||
| user | ||
| web_hooks | ||
| workflow | ||
| README.md | ||
Documentation
User documentation
- Account Security Securing your account via two-factor authentication, etc.
- API Automate GitLab via a simple and powerful API.
- CI/CD GitLab Continuous Integration (CI) and Continuous Delivery (CD) getting started,
.gitlab-ci.ymloptions, and examples. - GitLab as OAuth2 authentication service provider. It allows you to login to other applications from GitLab.
- Container Registry Learn how to use GitLab Container Registry.
- GitLab Basics Find step by step how to start working on your commandline and on GitLab.
- Importing to GitLab.
- Importing and exporting projects between instances.
- Markdown GitLab's advanced formatting system.
- Migrating from SVN Convert a SVN repository to Git and GitLab.
- Permissions Learn what each role in a project (external/guest/reporter/developer/master/owner) can do.
- Profile Settings
- Project Services Integrate a project with external services, such as CI and chat.
- Public access Learn how you can allow public and internal access to projects.
- SSH Setup your ssh keys and deploy keys for secure access to your projects.
- Webhooks Let GitLab notify you when new code has been pushed to your project.
- Workflow Using GitLab functionality and importing projects from GitHub and SVN.
Administrator documentation
- Access restrictions Define which Git access protocols can be used to talk to GitLab
- Authentication/Authorization Configure external authentication with LDAP, SAML, CAS and additional Omniauth providers.
- Custom Git hooks Custom Git hooks (on the filesystem) for when webhooks aren't enough.
- Install Requirements, directory structures and installation from source.
- Restart GitLab Learn how to restart GitLab and its components.
- Integration How to integrate with systems such as JIRA, Redmine, Twitter.
- Issue closing Customize how to close an issue from commit messages.
- Koding Set up Koding to use with GitLab.
- Libravatar Use Libravatar for user avatars.
- Log system Log system.
- Environment Variables to configure GitLab.
- Operations Keeping GitLab up and running.
- Raketasks Backups, maintenance, automatic webhook setup and the importing of projects.
- Repository checks Periodic Git repository checks.
- Repository storages Manage the paths used to store repositories.
- Security Learn what you can do to further secure your GitLab instance.
- System hooks Notifications when users, projects and keys are changed.
- Update Update guides to upgrade your installation.
- Welcome message Add a custom welcome message to the sign-in page.
- Reply by email Allow users to comment on issues and merge requests by replying to notification emails.
- Migrate GitLab CI to CE/EE Follow this guide to migrate your existing GitLab CI data to GitLab CE/EE.
- Git LFS configuration
- Housekeeping Keep your Git repository tidy and fast.
- GitLab Performance Monitoring Configure GitLab and InfluxDB for measuring performance metrics.
- Monitoring uptime Check the server status using the health check endpoint.
- Debugging Tips Tips to debug problems when things go wrong
- Sidekiq Troubleshooting Debug when Sidekiq appears hung and is not processing jobs.
- High Availability Configure multiple servers for scaling or high availability.
- Container Registry Configure Docker Registry with GitLab.
- Multiple mountpoints for the repositories storage Define multiple repository storage paths to distribute the storage load.
Contributor documentation
- Development All styleguides and explanations how to contribute.
- Legal Contributor license agreements.