diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-02-07 06:11:09 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-02-07 06:11:09 +0300 |
| commit | fcfafe81d1f1aa442c5a5c93cd27b5f5b798cb90 (patch) | |
| tree | c75080b3bf76b2a8f891e6b0b7437794da03519e /doc/user/group/compliance_frameworks.md | |
| parent | 11438b1771abda3c216ca627bf5319684474889b (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/group/compliance_frameworks.md')
| -rw-r--r-- | doc/user/group/compliance_frameworks.md | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/user/group/compliance_frameworks.md b/doc/user/group/compliance_frameworks.md index 6f048ae25b0..55bcb4ea1fb 100644 --- a/doc/user/group/compliance_frameworks.md +++ b/doc/user/group/compliance_frameworks.md @@ -274,3 +274,18 @@ Therefore, in projects with compliance frameworks, we recommend replacing pipeline feature. This alternative ensures the compliance pipeline does not re-start the parent pipeline. + +## Troubleshooting + +### Cannot remove compliance framework from a project + +If you move a project, the compliance framework can become orphaned and can't be removed. To manually remove a compliance framework from a project, run the following GraphQL +mutation with your project's ID: + +```graphql +mutation { + projectSetComplianceFramework(input: {projectId: "gid://gitlab/Project/1234567", complianceFrameworkId: null}) { + errors + } +} +``` |