Merge branch 'eread/remove-unnecessary-whitespace' into 'master'

Remove unnecessary whitespace from end of lines

See merge request gitlab-org/gitlab!60076

doc/administration/geo/replication/docker_registry.md

@@ -99,7 +99,7 @@ pair for all the sites. The **secondary** site will use this key to
 generate a short-lived JWT that is pull-only-capable to access the
 **primary** site Container Registry.
 
-For each application and Sidekiq node on the **secondary** site: 
+For each application and Sidekiq node on the **secondary** site:
 
 1. SSH into the node and login as the `root` user:
 

doc/administration/gitaly/configure_gitaly.md

@@ -979,7 +979,7 @@ identical fetches. It:
 The pack-objects cache is a local cache. It:
 
 - Stores its metadata in the memory of the Gitaly process it is enabled in.
-- Stores the actual Git data it is caching in files on local storage. 
+- Stores the actual Git data it is caching in files on local storage.
 
 Using local files has the benefit that the operating system may
 automatically keep parts of the pack-objects cache files in RAM,

doc/administration/monitoring/prometheus/gitlab_metrics.md

@@ -254,7 +254,7 @@ The following metrics are available:
 |:--------------------------------- |:--------- |:------------------------------------------------------------- |:-------------------------------------- |:--------------------------------------------------------- |
 | `db_load_balancing_hosts`         | Gauge     | [12.3](https://gitlab.com/gitlab-org/gitlab/-/issues/13630)   | Current number of load balancing hosts | |
 | `sidekiq_load_balancing_count`    | Counter   | 13.11                                                         | Sidekiq jobs using load balancing with data consistency set to :sticky or :delayed | `queue`, `boundary`, `external_dependencies`, `feature_category`, `job_status`, `urgency`, `data_consistency`, `database_chosen` |
- 
+
 ## Database partitioning metrics **(PREMIUM SELF)**
 
 The following metrics are available:

doc/administration/reference_architectures/10k_users.md

@@ -2363,7 +2363,7 @@ considered and customer technical support will be considered out of scope.
 As an alternative approach, you can also run select components of GitLab as Cloud Native
 in Kubernetes via our official [Helm Charts](https://docs.gitlab.com/charts/).
 In this setup, we support running the equivalent of GitLab Rails and Sidekiq nodes
-in a Kubernetes cluster, named Webservice and Sidekiq respectively. In addition, 
+in a Kubernetes cluster, named Webservice and Sidekiq respectively. In addition,
 the following other supporting services are supported: NGINX, Task Runner, Migrations,
 Prometheus and Grafana.
 

doc/api/runners.md

@@ -156,7 +156,7 @@ Example response:
 
 Get details of a runner.
 
-[Maintainer access or higher](../user/permissions.md) is required to get runner details at the project and group level. 
+[Maintainer access or higher](../user/permissions.md) is required to get runner details at the project and group level.
 
 Instance-level runner details via this endpoint are available to all signed in users.
 

doc/ci/services/gitlab.md

@@ -28,7 +28,7 @@ tests access to the GitLab API.
    [assign them to a variable in the user interface](../variables/README.md#project-cicd-variables).
    Then assign that variable to the corresponding variable in your
    `.gitlab-ci.yml` file.
-   
+
 Then, commands in `script:` sections in your `.gitlab-ci.yml` file can access the API at `http://gitlab/api/v4`.
 
 For more information about why `gitlab` is used for the `Host`, see

doc/development/cascading_settings.md

@@ -8,10 +8,10 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 > Introduced in [GitLab 13.11](https://gitlab.com/gitlab-org/gitlab/-/issues/321724).
 
-The cascading settings framework allows groups to essentially inherit settings 
-values from ancestors (parent group on up the group hierarchy) and from 
+The cascading settings framework allows groups to essentially inherit settings
+values from ancestors (parent group on up the group hierarchy) and from
 instance-level application settings. The framework also allows settings values
-to be enforced on groups lower in the hierarchy. 
+to be enforced on groups lower in the hierarchy.
 
 Cascading settings can currently only be defined within `NamespaceSetting`, though
 the framework may be extended to other objects in the future.
@@ -22,7 +22,7 @@ Settings are not cascading by default. To define a cascading setting, take the f
 
 1. In the `NamespaceSetting` model, define the new attribute using the `cascading_attr`
    helper method. You can use an array to define multiple attributes on a single line.
-   
+
     ```ruby
     class NamespaceSetting
       include CascadingNamespaceSettingAttribute
@@ -32,11 +32,11 @@ Settings are not cascading by default. To define a cascading setting, take the f
     ```
 
 1. Create the database columns.
-   
-   You can use the following database migration helper for a completely new setting. 
-   The helper creates four columns, two each in `namespace_settings` and 
+
+   You can use the following database migration helper for a completely new setting.
+   The helper creates four columns, two each in `namespace_settings` and
    `application_settings`.
-   
+
     ```ruby
     class AddDelayedProjectRemovalCascadingSetting < ActiveRecord::Migration[6.0]
       include Gitlab::Database::MigrationHelpers::CascadingNamespaceSettings
@@ -50,23 +50,23 @@ Settings are not cascading by default. To define a cascading setting, take the f
       end
     end
     ```
-   
+
    Existing settings being converted to a cascading setting will require individual
-   migrations to add columns and change existing columns. Use the specifications 
-   below to create migrations as required: 
-   
+   migrations to add columns and change existing columns. Use the specifications
+   below to create migrations as required:
+
     1. Columns in `namespace_settings` table:
         - `delayed_project_removal`: No default value. Null values allowed. Use any column type.
         - `lock_delayed_project_removal`: Boolean column. Default value is false. Null values not allowed.
     1. Columns in `application_settings` table:
-        - `delayed_project_removal`: Type matching for the column created in `namespace_settings`. 
-          Set default value as desired. Null values not allowed. 
-        - `lock_delayed_project_removal`: Boolean column. Default value is false. Null values not allowed. 
-        
+        - `delayed_project_removal`: Type matching for the column created in `namespace_settings`.
+          Set default value as desired. Null values not allowed.
+        - `lock_delayed_project_removal`: Boolean column. Default value is false. Null values not allowed.
+
 ## Convenience methods
 
 By defining an attribute using the `cascading_attr` method, a number of convenience
-methods are automatically defined. 
+methods are automatically defined.
 
 **Definition:**
 
@@ -88,7 +88,7 @@ The attribute reader method (`delayed_project_removal`) returns the correct
 cascaded value using the following criteria:
 
 1. Returns the dirty value, if the attribute has changed. This allows standard
-   Rails validators to be used on the attribute, though `nil` values *must* be allowed. 
+   Rails validators to be used on the attribute, though `nil` values *must* be allowed.
 1. Return locked ancestor value.
 1. Return locked instance-level application settings value.
 1. Return this namespace's attribute, if not nil.

doc/development/elasticsearch.md

@@ -241,8 +241,8 @@ cron worker runs. Default value is 5 minutes.
 - `pause_indexing!` - Pause indexing while the migration runs. This setting will record the indexing setting before
 the migration runs and set it back to that value when the migration is completed.
 
-- `space_requirements!` - Verify that enough free space is available in the cluster when the migration runs. This setting 
-  will halt the migration if the storage required is not available when the migration runs. The migration must provide 
+- `space_requirements!` - Verify that enough free space is available in the cluster when the migration runs. This setting
+  will halt the migration if the storage required is not available when the migration runs. The migration must provide
   the space required in bytes by defining a `space_required_bytes` method.
 
 ```ruby

doc/development/fe_guide/vue.md

@@ -102,9 +102,9 @@ across the codebase.
 #### Providing Rails form fields to Vue applications
 
 When composing a form with Rails, the `name`, `id`, and `value` attributes of form inputs are generated
-to match the backend. It can be helpful to have access to these generated attributes when converting 
+to match the backend. It can be helpful to have access to these generated attributes when converting
 a Rails form to Vue, or when [integrating components (datepicker, project selector, etc)](https://gitlab.com/gitlab-org/gitlab/-/blob/8956ad767d522f37a96e03840595c767de030968/app/assets/javascripts/access_tokens/index.js#L15) into it.
-The [`parseRailsFormFields`](https://gitlab.com/gitlab-org/gitlab/-/blob/fe88797f682c7ff0b13f2c2223a3ff45ada751c1/app/assets/javascripts/lib/utils/forms.js#L107) utility can be used to parse the generated form input attributes so they can be passed to the Vue application. 
+The [`parseRailsFormFields`](https://gitlab.com/gitlab-org/gitlab/-/blob/fe88797f682c7ff0b13f2c2223a3ff45ada751c1/app/assets/javascripts/lib/utils/forms.js#L107) utility can be used to parse the generated form input attributes so they can be passed to the Vue application.
 This allows us to easily integrate Vue components without changing how the form submits.
 
 ```haml
@@ -116,7 +116,7 @@ This allows us to easily integrate Vue components without changing how the form
 ```
 
 > The `js_name` data attribute is used as the key in the resulting JavaScript object.
-For example `= form.text_field :email, data: { js_name: 'fooBarBaz' }` would be translated 
+For example `= form.text_field :email, data: { js_name: 'fooBarBaz' }` would be translated
 to `{ fooBarBaz: { name: 'user[email]', id: 'user_email', value: '' } }`
 
 ```javascript

doc/development/graphql_guide/authorization.md

@@ -148,7 +148,7 @@ end
 ```
 
 In this example, we use field authorization (such as
-`Ability.allowed?(current_user, :read_transactions, bank_account)`) to avoid 
+`Ability.allowed?(current_user, :read_transactions, bank_account)`) to avoid
 a more expensive query:
 
 ```ruby

doc/development/pipelines.md

@@ -436,7 +436,7 @@ This mapping is currently generated using a combination of test coverage tracing
 In the `detect-tests` job, we use this mapping to identify the minimal tests needed for the current Merge Request.
 
 In this experiment, each `rspec` job is accompanied with a `minimal` version.
-For example, `rspec unit` job has a corresponding `rspec unit minimal` job. 
+For example, `rspec unit` job has a corresponding `rspec unit minimal` job.
 During the experiment, each Merge Request pipeline will contain both versions of the job, running in parallel.
 
 To illustrate this:
@@ -462,7 +462,7 @@ graph LR
 ```
 
 The result of both set of jobs in the pipeline is then compared to identify any false positive.
-A list of such pipeline can be found in [Sisense](https://app.periscopedata.com/app/gitlab/496118/Engineering-Productivity-Sandbox?widget=10492739&udv=833427). 
+A list of such pipeline can be found in [Sisense](https://app.periscopedata.com/app/gitlab/496118/Engineering-Productivity-Sandbox?widget=10492739&udv=833427).
 
 A false positive is defined as a pipeline where the `minimal` jobs passed, but the non-`minimal` jobs failed.
 This indicates that the changeset resulted in a test failure, which was not detected by the `minimal` jobs.

doc/development/testing_guide/frontend_testing.md

@@ -1151,8 +1151,8 @@ Both functions run `callback` on the next tick after the requests finish (using
 
 ### `shallowMountExtended` and `mountExtended`
 
-The `shallowMountExtended` and `mountExtended` utilities provide you with the ability to perform 
-any of the available [DOM Testing Library queries](https://testing-library.com/docs/queries/about) 
+The `shallowMountExtended` and `mountExtended` utilities provide you with the ability to perform
+any of the available [DOM Testing Library queries](https://testing-library.com/docs/queries/about)
 by prefixing them with `find` or `findAll`.
 
 ```javascript

doc/install/aws/index.md

@@ -841,6 +841,6 @@ If you see this page when trying to set a password via the web interface, make s
 
 ### Some job logs are not uploaded to object storage
 
-When the GitLab deployment is scaled up to more than one node, some job logs may not be uploaded to [object storage](../../administration/object_storage.md) properly. [Incremental logging is required](../../administration/object_storage.md#incremental-logging-is-required-for-ci-to-use-object-storage) for CI to use object storage. 
+When the GitLab deployment is scaled up to more than one node, some job logs may not be uploaded to [object storage](../../administration/object_storage.md) properly. [Incremental logging is required](../../administration/object_storage.md#incremental-logging-is-required-for-ci-to-use-object-storage) for CI to use object storage.
 
-Enable [incremental logging](../../administration/job_logs.md#enabling-incremental-logging) if it has not already been enabled. 
+Enable [incremental logging](../../administration/job_logs.md#enabling-incremental-logging) if it has not already been enabled.

doc/operations/incident_management/integrations.md

@@ -168,7 +168,7 @@ alert to confirm your integration works properly.
 1. Sign in as a user with Developer or greater [permissions](../../user/permissions.md).
 1. Navigate to **Settings > Operations** in your project.
 1. Click **Alert integrations** to expand the section.
-1. Click the **{settings}** settings icon on the right side of the integration in [the list](#integrations-list). 
+1. Click the **{settings}** settings icon on the right side of the integration in [the list](#integrations-list).
 1. Select the **Send test alert** tab to open it.
 1. Enter a test payload in the payload field (valid JSON is required).
 1. Click **Send**.

doc/topics/git/numerous_undo_possibilities_in_git/index.md

@@ -379,7 +379,7 @@ it also provides a clear timeline and development structure.
 
 ![Use revert to keep branch flowing](img/revert.png)
 
-If you want to revert changes introduced in certain `commit-id`, you can 
+If you want to revert changes introduced in certain `commit-id`, you can
 revert that `commit-id` (swap additions and deletions) in newly created commit:
 You can do this with
 

doc/update/restore_after_failure.md

@@ -12,7 +12,7 @@ However, it's important to know how to recover when problems do arise.
 ## Roll back to an earlier version and restore a backup
 
 In some cases after a failed upgrade, the fastest solution is to roll back to
-the previous version you were using. We recommend this path because the failed 
+the previous version you were using. We recommend this path because the failed
 upgrade will likely have made database changes that can not be readily reverted.
 
 First, roll back the code or package. For source installations this involves

doc/user/application_security/api_fuzzing/index.md

@@ -1157,7 +1157,7 @@ For OpenAPI specifications that are generated automatically validation errors ar
   - `OpenAPI 2.0 schema validation error ...`
   - `OpenAPI 3.0.x schema validation error ...`
 
-**Solution** 
+**Solution**
 
 **For generated OpenAPI specifications**
 
@@ -1183,7 +1183,7 @@ The API Fuzzing engine outputs an error message when it cannot establish a conne
 - In [GitLab 13.11 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/323939), `Failed to start scanner session (version header not found).`
 - In GitLab 13.10 and earlier, `API Security version header not found.  Are you sure that you are connecting to the API Security server?`.
 
-**Solution** 
+**Solution**
 
 - Remove the `FUZZAPI_API` variable from the `.gitlab-ci.yml` file. The value will be inherited from the API Fuzzing CI/CD template. We recommend this method instead of manually setting a value.
 - If removing the variable is not possible, check to see if this value has changed in the latest version of the [API Fuzzing CI/CD template](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Security/API-Fuzzing.gitlab-ci.yml). If so, update the value in the `.gitlab-ci.yml` file.

doc/user/application_security/dast/index.md

@@ -948,11 +948,11 @@ A site profile contains the following:
 - **Excluded URLs**: A comma-separated list of URLs to exclude from the scan.
 - **Request headers**: A comma-separated list of HTTP request headers, including names and values. These headers are added to every request made by DAST.
 - **Authentication**:  
-  - **Authenticated URL**: The URL of the page containing the sign-in HTML form on the target website. The username and password are submitted with the login form to create an authenticated scan. 
+  - **Authenticated URL**: The URL of the page containing the sign-in HTML form on the target website. The username and password are submitted with the login form to create an authenticated scan.
   - **Username**: The username used to authenticate to the website.
   - **Password**: The password used to authenticate to the website.
-  - **Username form field**: The name of username field at the sign-in HTML form. 
-  - **Password form field**: The name of password field at the sign-in HTML form. 
+  - **Username form field**: The name of username field at the sign-in HTML form.
+  - **Password form field**: The name of password field at the sign-in HTML form.
 
 #### Site profile validation
 

doc/user/application_security/sast/analyzers.md

@@ -45,7 +45,7 @@ GitLab, but users can also integrate their own **custom images**.
 
 ## SAST analyzer features
 
-For an analyzer to be considered Generally Available, it is expected to minimally 
+For an analyzer to be considered Generally Available, it is expected to minimally
 support the following features:
 
 - [Customizable configuration](index.md#available-variables)

doc/user/compliance/license_compliance/index.md

@@ -766,7 +766,7 @@ Defining a non-latest Python version in ASDF_PYTHON_VERSION [doesn't have it aut
 1. Define the required version by setting the `ASDF_PYTHON_VERSION` CI/CD variable.
 1. Pass a custom script to the `SETUP_CMD` CI/CD variable to install the required version and dependencies.
 
-For example: 
+For example:
 
 ```yaml
 include:

doc/user/project/import/github.md

@@ -69,7 +69,7 @@ must meet one of the following conditions prior to the import:
   GitLab content imports that use GitHub accounts require that the GitHub public-facing
   email address is populated so that all comments and contributions are properly mapped
   to the same user in GitLab. GitHub Enterprise (on premise) does not require this field
-  to be populated to use the product, so you may need to add it on existing GitHub Enterprise 
+  to be populated to use the product, so you may need to add it on existing GitHub Enterprise
   accounts for imported content to be properly mapped to the user in the new system.
   Refer to GitHub documentation for instructions on how to add that address.
 

doc/user/project/time_tracking.md

@@ -56,7 +56,7 @@ To remove an estimation entirely, use `/remove_estimate`.
 
 ### Time spent
 
-To enter time spent, write `/spend`, followed by the time. For example, if you need 
+To enter time spent, write `/spend`, followed by the time. For example, if you need
 to log 1 month, 2 weeks, 3 days, 4 hours and 5 minutes, you would write `/spend 1mo 2w 3d 4h 5m`.
 Time units that we support are listed at the bottom of this help page.
 
@@ -68,7 +68,7 @@ days from the total time spent. You can't go below 0 minutes of time spent,
 so GitLab automatically resets the time spent if you remove a larger amount
 of time compared to the time that was entered already.
 
-You can log time in the past by providing a date after the time. 
+You can log time in the past by providing a date after the time.
 For example, if you want to log 1 hour of time spent on the 31 January 2021,
 you would write `/spend 1h 2021-01-31`. If you supply a date in the future, the
 command fails and no time is logged.