GitLab merge requestshttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests2024-03-07T17:12:03Zhttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3167Master llm summary check2024-03-07T17:12:03ZPhil Hughesme@iamphill.comMaster llm summary check## 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/3166Update README.md2023-12-04T15:18:04ZReuben PereiraUpdate 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?Reuben PereiraReuben Pereirahttps://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3165Resolve vulnerability: Function Call Object Injection Sink2023-11-14T14:14:27ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3164Resolve vulnerability: Function Call Object Injection Sink2023-11-14T14:14:27ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3163Resolve vulnerability: Function Call Object Injection Sink2023-11-14T14:13:54ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3162Resolve vulnerability: Function Call Object Injection Sink2023-11-14T14:13:58ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3161Resolve vulnerability: Function Call Object Injection Sink2023-11-14T14:12:48ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3160Resolve vulnerability: Function Call Object Injection Sink2023-11-14T14:12:49ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3159Resolve vulnerability: Function Call Object Injection Sink2023-11-14T14:06:55ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3157Resolve vulnerability: Function Call Object Injection Sink2023-11-14T14:07:08ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3158Resolve vulnerability: Function Call Object Injection Sink2023-11-14T14:07:09ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3156Resolve vulnerability: Function Call Object Injection Sink2023-11-14T13:52:45ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3155Resolve vulnerability: Function Call Object Injection Sink2023-11-14T13:52:17ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3154Resolve vulnerability: Function Call Object Injection Sink2023-11-14T13:49:15ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3153Resolve vulnerability: Function Call Object Injection Sink2023-11-14T13:49:10ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3152Resolve vulnerability: Function Call Object Injection Sink2023-11-14T13:49:21ZGregory HavengaResolve vulnerability: Function Call Object Injection Sink## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve...## AI GENERATED PATCH
The suggested code changes in this MR were produced by using the GitLab Duo Resolve this vulnerability feature, using AI. Before you apply the code changes, carefully review and test them, to ensure that they solve the vulnerability, don't harm the functional behaviour of your application or introduce new vulnerabilities.
The large language model that generated the suggested code changes was only provided with the affected lines of code, and the vulnerability in that code. It is not aware of any functionality outside of this context.
### Description:
Bracket object notation with user input is present, this might allow an attacker to access all properties of the object and even it's prototype, leading to possible code execution.
* Severity: Critical
* Confidence: Unknown
* Location: [app/assets/javascripts/lib/utils/url_utility.js:547](app/assets/javascripts/lib/utils/url_utility.js:547)
### Identifiers:
* [ESLint rule ID security/detect-object-injection](https://github.com/nodesecurity/eslint-plugin-security#detect-object-injection)
* [CWE-94](https://cwe.mitre.org/data/definitions/94.html)https://staging.gitlab.com/gitlab-org/gitlab/-/merge_requests/3149Update README.md2023-06-07T13:30:42ZDiana ZubovaUpdate 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?Diana ZubovaDiana Zubovahttps://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?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/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?