chore: only run CQA analysis for main and future branches, not the older ones where we didn't implement CQA scripts; also checkout build scripts from the PR's base branch, not main, so we get the correct tooling

[nickboldt]

1. Only run CQA analysis for main and future branches, not the older ones where we didn't implement CQA scripts
2. Checkout trusted build scripts from the PR's base branch, not main, so we get the correct tooling

https://redhat.atlassian.net/browse/RHIDP-12990

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s):

Issue:

Preview:

[rhdh-bot]

Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-2063/ @ 4/16/2026, 6:45:23 PM

[rhdh-bot]

/lgtm
/approve

[nickboldt]

/cherry-pick release-1.8
/cherry-pick release-1.9

[openshift-cherrypick-robot]

@nickboldt: once the present PR merges, I will cherry-pick it on top of release-1.8, release-1.9 in new PRs and assign them to you.

Details

In response to this:

/cherry-pick release-1.8
/cherry-pick release-1.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

New changes are detected. LGTM label has been removed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[openshift-cherrypick-robot]

@nickboldt: #2063 failed to apply on top of branch "release-1.9":

Applying: chore: only run CQA analysis for main and future branches, not the older ones.
Using index info to reconstruct a base tree...
A	.github/workflows/content-quality-assessment.yml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): .github/workflows/content-quality-assessment.yml deleted in HEAD and modified in chore: only run CQA analysis for main and future branches, not the older ones.. Version chore: only run CQA analysis for main and future branches, not the older ones. of .github/workflows/content-quality-assessment.yml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 chore: only run CQA analysis for main and future branches, not the older ones.

Details

In response to this:

/cherry-pick release-1.8
/cherry-pick release-1.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@nickboldt: #2063 failed to apply on top of branch "release-1.8":

Applying: chore: only run CQA analysis for main and future branches, not the older ones.
Using index info to reconstruct a base tree...
A	.github/workflows/content-quality-assessment.yml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): .github/workflows/content-quality-assessment.yml deleted in HEAD and modified in chore: only run CQA analysis for main and future branches, not the older ones.. Version chore: only run CQA analysis for main and future branches, not the older ones. of .github/workflows/content-quality-assessment.yml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 chore: only run CQA analysis for main and future branches, not the older ones.

Details

In response to this:

/cherry-pick release-1.8
/cherry-pick release-1.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.