GitLab merge requestshttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests2021-08-06T03:24:48Zhttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3126Resolve vulnerability: Cross-site Scripting in mermaid2021-08-06T03:24:48ZGitLab Security BotResolve vulnerability: Cross-site Scripting in mermaid### Description:
Mermaid allows XSS when the antiscript feature is used.
* Severity: medium
* Confidence: unknown
* Location: [yarn.lock](yarn.lock)
### Solution:
Upgrade to version 8.11.0 or above.
### Identifiers:
* [Gemnasium-53...### Description:
Mermaid allows XSS when the antiscript feature is used.
* Severity: medium
* Confidence: unknown
* Location: [yarn.lock](yarn.lock)
### Solution:
Upgrade to version 8.11.0 or above.
### Identifiers:
* [Gemnasium-53c99488-c5d6-4392-89c7-7e470e347b92](https://gitlab.com/gitlab-org/security-products/gemnasium-db/-/blob/master/npm/mermaid/CVE-2021-35513.yml)
* [CVE-2021-35513](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35513)
### Links:
* https://nvd.nist.gov/vuln/detail/CVE-2021-35513https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3127Resolve vulnerability: Improper Input Validation in minimist2021-08-06T03:25:03ZGitLab Security BotResolve vulnerability: Improper Input Validation in minimist### Description:
minimist could be tricked into adding or modifying properties of `Object.prototype` using a `constructor` or `__proto__` payload.
* Severity: medium
* Confidence: unknown
* Location: [yarn.lock](yarn.lock)
### Solutio...### Description:
minimist could be tricked into adding or modifying properties of `Object.prototype` using a `constructor` or `__proto__` payload.
* Severity: medium
* Confidence: unknown
* Location: [yarn.lock](yarn.lock)
### Solution:
Upgrade to version 1.2.2 or above.
### Identifiers:
* [Gemnasium-53e8766c-27eb-4278-8c4f-3dcef53a68bf](https://gitlab.com/gitlab-org/security-products/gemnasium-db/-/blob/master/npm/minimist/CVE-2020-7598.yml)
* [CVE-2020-7598](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7598)
### Links:
* https://nvd.nist.gov/vuln/detail/CVE-2020-7598https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3128Resolve vulnerability: Uncontrolled Search Path Element in execa2021-08-06T03:25:16ZGitLab Security BotResolve vulnerability: Uncontrolled Search Path Element in execa### Description:
Attackers could trick execa into executing arbitrary binaries. This behaviour is caused by the setting `preferLocal=true` which makes execa search for locally installed binaries and executes them. This vulnerability is ...### Description:
Attackers could trick execa into executing arbitrary binaries. This behaviour is caused by the setting `preferLocal=true` which makes execa search for locally installed binaries and executes them. This vulnerability is usually only exploitable when using execa on a client-side LOCAL application.
* Severity: critical
* Confidence: unknown
* Location: [storybook/yarn.lock](storybook/yarn.lock)
### Solution:
Upgrade to version 2.0.0 or above.
### Identifiers:
* [Gemnasium-05cfa2e8-2d0c-42c1-8894-638e2f12ff3d](https://gitlab.com/gitlab-org/security-products/gemnasium-db/-/blob/master/npm/execa/GMS-2020-2.yml)
### Links:
* https://github.com/sindresorhus/execa/releases/tag/v2.0.0https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3129Resolve vulnerability: Prototype Pollution in aws-sdk2021-08-06T03:25:31ZGitLab Security BotResolve vulnerability: Prototype Pollution in aws-sdk### Description:
If an attacker submits a malicious INI file to an application that parses it with `loadSharedConfigFiles`, they will pollute the prototype on the application. This can be exploited further depending on the context.
* S...### Description:
If an attacker submits a malicious INI file to an application that parses it with `loadSharedConfigFiles`, they will pollute the prototype on the application. This can be exploited further depending on the context.
* Severity: critical
* Confidence: unknown
* Location: [yarn.lock](yarn.lock)
### Solution:
Upgrade to version 2.814.0 or above.
### Identifiers:
* [Gemnasium-3d4bca0d-97ee-47a5-9251-a7924d950785](https://gitlab.com/gitlab-org/security-products/gemnasium-db/-/blob/master/npm/aws-sdk/CVE-2020-28472.yml)
* [CVE-2020-28472](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28472)
### Links:
* https://nvd.nist.gov/vuln/detail/CVE-2020-28472https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3130Resolve vulnerability: Improper Certificate Validation in xmlhttprequest-ssl2021-08-06T03:25:45ZGitLab Security BotResolve vulnerability: Improper Certificate Validation in xmlhttprequest-ssl### Description:
The xmlhttprequest-ssl package for Node.js disables SSL certificate validation by default, because `rejectUnauthorized` (when the property exists but is undefined) is considered to be false within the `https.request` fu...### Description:
The xmlhttprequest-ssl package for Node.js disables SSL certificate validation by default, because `rejectUnauthorized` (when the property exists but is undefined) is considered to be false within the `https.request` function of Node.js. In other words, no certificate is ever rejected.
* Severity: critical
* Confidence: unknown
* Location: [yarn.lock](yarn.lock)
### Solution:
Upgrade to version 1.6.1 or above.
### Identifiers:
* [Gemnasium-204c0a15-a193-4adf-a4dd-61d5d54f8097](https://gitlab.com/gitlab-org/security-products/gemnasium-db/-/blob/master/npm/xmlhttprequest-ssl/CVE-2021-31597.yml)
* [CVE-2021-31597](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-31597)
### Links:
* https://nvd.nist.gov/vuln/detail/CVE-2021-31597https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3131Update .gitlab-ci.yml2021-08-23T14:15:28ZMaxime OreficeUpdate .gitlab-ci.yml## What does this MR do?
[Testing tags limit](https://gitlab.com/gitlab-org/gitlab/-/issues/338479).## What does this MR do?
[Testing tags limit](https://gitlab.com/gitlab-org/gitlab/-/issues/338479).https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3132Update .rubocop.yml2021-09-27T11:04:18Zusername-removed-443319Update .rubocop.yml## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [ ] Tests added for this feature/bug
- Review
- [ ] Has been reviewed by UX
- [ ] Has been reviewed by Frontend
- [ ] Has been reviewed by Backend
- [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3134Update README.md2021-10-20T22:03:59ZSean ArnoldUpdate README.md## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [ ] Tests added for this feature/bug
- Review
- [ ] Has been reviewed by UX
- [ ] Has been reviewed by Frontend
- [ ] Has been reviewed by Backend
- [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?Sean ArnoldSean Arnoldhttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3135Update main.js2023-03-27T10:09:13ZPhil Hughesme@iamphill.comUpdate main.js## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [ ] Tests added for this feature/bug
- Review
- [ ] Has been reviewed by UX
- [ ] Has been reviewed by Frontend
- [ ] Has been reviewed by Backend
- [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?Phil Hughesme@iamphill.comPhil Hughesme@iamphill.comhttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3136Update usage_data.rb2021-12-07T15:50:51ZPiotr SkorupaUpdate usage_data.rb## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [ ] Tests added for this feature/bug
- Review
- [ ] Has been reviewed by UX
- [ ] Has been reviewed by Frontend
- [ ] Has been reviewed by Backend
- [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?Piotr SkorupaPiotr Skorupahttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3137Test MR2022-01-06T06:37:38ZStan HuTest MRTestTesthttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3138Update README.md2023-06-27T10:14:43ZPhil Hughesme@iamphill.comUpdate README.md## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [ ] Tests added for this feature/bug
- Review
- [ ] Has been reviewed by UX
- [ ] Has been reviewed by Frontend
- [ ] Has been reviewed by Backend
- [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?2018 Q3Phil Hughesme@iamphill.comPhil Hughesme@iamphill.comhttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3139Test coverage pipeline MR2022-03-15T15:56:35ZNikola MilojevicTest coverage pipeline MR## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [ ] Tests added for this feature/bug
- Review
- [ ] Has been reviewed by UX
- [ ] Has been reviewed by Frontend
- [ ] Has been reviewed by Backend
- [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?Nikola MilojevicNikola Milojevichttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3140Update .gitignore, app/assets/javascripts/diffs/components/diff_row.vue2023-05-12T16:11:15ZAndré LuísUpdate .gitignore, app/assets/javascripts/diffs/components/diff_row.vue## What does this MR do and why?
Just a default MR.
_Describe in detail what your merge request does and why._
<!--
Please keep this description updated with any discussion that takes place so
that reviewers can understand your intent...## What does this MR do and why?
Just a default MR.
_Describe in detail what your merge request does and why._
<!--
Please keep this description updated with any discussion that takes place so
that reviewers can understand your intent. Keeping the description updated is
especially important if they didn't participate in the discussion.
-->
## Screenshots or screen recordings
_These are strongly recommended to assist reviewers and reduce the time to merge your change._
<!--
Please include any relevant screenshots or screen recordings that will assist
reviewers and future readers. If you need help visually verifying the change,
please leave a comment and ping a GitLab reviewer, maintainer, or MR coach.
-->
## How to set up and validate locally
_Numbered steps to set up and validate the change are strongly suggested._
<!--
Example below:
1. Enable the invite modal
```ruby
Feature.enable(:invite_members_group_modal)
```
1. In rails console enable the experiment fully
```ruby
Feature.enable(:member_areas_of_focus)
```
1. Visit any group or project member pages such as `http://127.0.0.1:3000/groups/flightjs/-/group_members`
1. Click the `invite members` button.
-->
## MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
* [ ] I have evaluated the [MR acceptance checklist](https://docs.gitlab.com/ee/development/code_review.html#acceptance-checklist) for this MR.
<!-- template sourced from https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/merge_request_templates/Default.md -->André LuísAndré Luíshttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3142Add new file2022-07-18T17:37:12ZAllison BrowneAdd new file## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [ ] Tests added for this feature/bug
- Review
- [ ] Has been reviewed by UX
- [ ] Has been reviewed by Frontend
- [ ] Has been reviewed by Backend
- [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3143Update README.md2023-10-18T09:26:07ZMarc ShawUpdate README.md## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [ ] Tests added for this feature/bug
- Review
- [ ] Has been reviewed by UX
- [ ] Has been reviewed by Frontend
- [ ] Has been reviewed by Backend
- [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3144Update settings.json2023-04-07T17:30:51ZMario Sebastián Celi CalderónUpdate settings.json## What does this MR do?
Updating description of the MR
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] ...## What does this MR do?
Updating description of the MR
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [ ] Tests added for this feature/bug
- Review
- [ ] Has been reviewed by UX
- [ ] Has been reviewed by Frontend
- [ ] Has been reviewed by Backend
- [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3146Draft: Test resource groups2023-02-20T15:27:42ZHalil CobanDraft: Test resource groups## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [ ] Tests added for this feature/bug
- Review
- [ ] Has been reviewed by UX
- [ ] Has been reviewed by Frontend
- [ ] Has been reviewed by Backend
- [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3147Update README.md2023-05-02T18:51:50ZJose Ivan Vargas LopezUpdate README.md## What does this MR do?
**DO NOT MERGE** This is just for testing purposes
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the accepta...## What does this MR do?
**DO NOT MERGE** This is just for testing purposes
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [ ] Tests added for this feature/bug
- Review
- [ ] Has been reviewed by UX
- [ ] Has been reviewed by Frontend
- [ ] Has been reviewed by Backend
- [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?Jose Ivan Vargas LopezJose Ivan Vargas Lopezhttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3148Add new file2023-08-04T09:06:41ZPhil Hughesme@iamphill.comAdd new file## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ee/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://docs.gitlab.com/ee/development/doc_styleguide.html)
- [ ] API support added
- [ ] Tests added for this feature/bug
- Review
- [ ] Has been reviewed by UX
- [ ] Has been reviewed by Frontend
- [ ] Has been reviewed by Backend
- [ ] Has been reviewed by Database
- [ ] Conform by the [merge request performance guides](https://docs.gitlab.com/ee/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CONTRIBUTING.md#style-guides)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?