Remove trailing whitespace in docs
Remove unneeded trailing whitespace in lines in /development /ci /api and /administration docs.
This commit is contained in:
Marcel Amirault
Achilleas Pipinellis
parent
2b4521c165
commit
143872fa52
23 changed files with 136 additions and 142 deletions
|
|
@ -701,7 +701,6 @@ To get around this, you can [change the group path](../user/group/index.md#chang
|
|||
branch name. Another option is to create a [push rule](../push_rules/push_rules.html) to prevent
|
||||
this at the instance level.
|
||||
|
||||
|
||||
[ce-18239]: https://gitlab.com/gitlab-org/gitlab-ce/issues/18239
|
||||
[docker-insecure-self-signed]: https://docs.docker.com/registry/insecure/#use-self-signed-certificates
|
||||
[reconfigure gitlab]: restart_gitlab.md#omnibus-gitlab-reconfigure
|
||||
|
|
|
|||
|
|
@ -211,4 +211,3 @@ separately:
|
|||
1. [Configure the GitLab application servers](gitlab.md)
|
||||
1. [Configure the load balancers](load_balancer.md)
|
||||
1. [Monitoring node (Prometheus and Grafana)](monitoring_node.md)
|
||||
|
||||
|
|
|
|||
|
|
@ -84,7 +84,6 @@ export ID_TO=50
|
|||
You can monitor the progress in the **Admin Area > Monitoring > Background Jobs** page.
|
||||
On the **Queues** tab, you can watch the `hashed_storage:hashed_storage_project_rollback` queue to see how long the process will take to finish.
|
||||
|
||||
|
||||
After it reaches zero, you can confirm every project has been rolled back by running the commands bellow.
|
||||
If some projects weren't rolled back, you can run this rollback script again to schedule further rollbacks.
|
||||
|
||||
|
|
@ -106,7 +105,7 @@ sudo gitlab-rake gitlab:storage:legacy_projects
|
|||
sudo -u git -H bundle exec rake gitlab:storage:legacy_projects RAILS_ENV=production
|
||||
```
|
||||
|
||||
------
|
||||
---
|
||||
|
||||
To list projects using **Legacy** storage:
|
||||
|
||||
|
|
@ -139,7 +138,7 @@ sudo gitlab-rake gitlab:storage:hashed_projects
|
|||
sudo -u git -H bundle exec rake gitlab:storage:hashed_projects RAILS_ENV=production
|
||||
```
|
||||
|
||||
------
|
||||
---
|
||||
|
||||
To list projects using **Hashed** storage:
|
||||
|
||||
|
|
@ -171,7 +170,7 @@ sudo gitlab-rake gitlab:storage:legacy_attachments
|
|||
sudo -u git -H bundle exec rake gitlab:storage:legacy_attachments RAILS_ENV=production
|
||||
```
|
||||
|
||||
------
|
||||
---
|
||||
|
||||
To list project attachments using **Legacy** storage:
|
||||
|
||||
|
|
@ -203,7 +202,7 @@ sudo gitlab-rake gitlab:storage:hashed_attachments
|
|||
sudo -u git -H bundle exec rake gitlab:storage:hashed_attachments RAILS_ENV=production
|
||||
```
|
||||
|
||||
------
|
||||
---
|
||||
|
||||
To list project attachments using **Hashed** storage:
|
||||
|
||||
|
|
|
|||
|
|
@ -62,4 +62,3 @@ close the terminal window.
|
|||
## Interactive Web Terminals for the Web IDE **(ULTIMATE ONLY)**
|
||||
|
||||
Read the Web IDE docs to learn how to run [Interactive Terminals through the Web IDE](../../user/project/web_ide/index.md).
|
||||
|
||||
|
|
|
|||
|
|
@ -98,7 +98,6 @@ indicate if an issue needs backend work, frontend work, or both.
|
|||
Team labels are always capitalized so that they show up as the first label for
|
||||
any issue.
|
||||
|
||||
|
||||
## Stage labels
|
||||
|
||||
Stage labels specify which [DevOps stage][devops-stages] the issue belongs to.
|
||||
|
|
@ -141,42 +140,41 @@ Group labels specify which [groups][structure-groups] the issue belongs to.
|
|||
|
||||
The current group labels are:
|
||||
|
||||
* ~"group::access"
|
||||
* ~"group::measure"
|
||||
* ~"group::source code"
|
||||
* ~"group::knowledge"
|
||||
* ~"group::editor"
|
||||
* ~"group::gitaly"
|
||||
* ~"group::gitter"
|
||||
* ~"group::team planning"
|
||||
* ~"group::enterprise planning"
|
||||
* ~"group::certify"
|
||||
* ~"group::ci and runner"
|
||||
* ~"group::testing"
|
||||
* ~"group::package"
|
||||
* ~"group::progressive delivery"
|
||||
* ~"group::release management"
|
||||
* ~"group::autodevops and kubernetes"
|
||||
* ~"group::serverless and paas"
|
||||
* ~"group::apm"
|
||||
* ~"group::health"
|
||||
* ~"group::static analysis"
|
||||
* ~"group::dynamic analysis"
|
||||
* ~"group::software composition analysis"
|
||||
* ~"group::runtime application security"
|
||||
* ~"group::threat management"
|
||||
* ~"group::application infrastructure security"
|
||||
* ~"group::activation"
|
||||
* ~"group::adoption"
|
||||
* ~"group::upsell"
|
||||
* ~"group::retention"
|
||||
* ~"group::fulfillment"
|
||||
* ~"group::telemetry"
|
||||
* ~"group::distribution"
|
||||
* ~"group::geo"
|
||||
* ~"group::memory"
|
||||
* ~"group::ecosystem"
|
||||
|
||||
- ~"group::access"
|
||||
- ~"group::measure"
|
||||
- ~"group::source code"
|
||||
- ~"group::knowledge"
|
||||
- ~"group::editor"
|
||||
- ~"group::gitaly"
|
||||
- ~"group::gitter"
|
||||
- ~"group::team planning"
|
||||
- ~"group::enterprise planning"
|
||||
- ~"group::certify"
|
||||
- ~"group::ci and runner"
|
||||
- ~"group::testing"
|
||||
- ~"group::package"
|
||||
- ~"group::progressive delivery"
|
||||
- ~"group::release management"
|
||||
- ~"group::autodevops and kubernetes"
|
||||
- ~"group::serverless and paas"
|
||||
- ~"group::apm"
|
||||
- ~"group::health"
|
||||
- ~"group::static analysis"
|
||||
- ~"group::dynamic analysis"
|
||||
- ~"group::software composition analysis"
|
||||
- ~"group::runtime application security"
|
||||
- ~"group::threat management"
|
||||
- ~"group::application infrastructure security"
|
||||
- ~"group::activation"
|
||||
- ~"group::adoption"
|
||||
- ~"group::upsell"
|
||||
- ~"group::retention"
|
||||
- ~"group::fulfillment"
|
||||
- ~"group::telemetry"
|
||||
- ~"group::distribution"
|
||||
- ~"group::geo"
|
||||
- ~"group::memory"
|
||||
- ~"group::ecosystem"
|
||||
|
||||
These labels are [scoped labels](../../user/project/labels.md#scoped-labels-premium)
|
||||
and thus are mutually exclusive.
|
||||
|
|
@ -192,15 +190,15 @@ can be applied to a single issue. You can find the groups listed in the
|
|||
|
||||
The current department labels are:
|
||||
|
||||
* ~UX
|
||||
* ~Quality
|
||||
- ~UX
|
||||
- ~Quality
|
||||
|
||||
## Specialization labels
|
||||
|
||||
These labels narrow the [specialization](https://about.gitlab.com/company/team/structure/#specialist) on a unit of work.
|
||||
|
||||
* ~frontend
|
||||
* ~backend
|
||||
- ~frontend
|
||||
- ~backend
|
||||
|
||||
## Release Scoping labels
|
||||
|
||||
|
|
|
|||
|
|
@ -133,5 +133,4 @@ are very appreciative of the work done by translators and proofreaders!
|
|||
- When a request is made for the first proofreader for a language and there are no [GitLab team members](https://about.gitlab.com/team/)
|
||||
or [Core team members](https://about.gitlab.com/core-team/) who speak the language, we will request links to previous translation work in other communities or projects.
|
||||
|
||||
|
||||
[proofreader-src]: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/i18n/proofreader.md
|
||||
|
|
|
|||
|
|
@ -28,6 +28,7 @@ Updates all currently staged files (based on `git diff`) with Prettier and saves
|
|||
```
|
||||
yarn prettier-staged
|
||||
```
|
||||
|
||||
Checks all currently staged files (based on `git diff`) with Prettier and log which files would need manual updating to the console.
|
||||
|
||||
```
|
||||
|
|
|
|||
Loading…
Reference in a new issue