ci: add release-2.1 branch to intelligent assistant action workflow

[Jdubrick]

Description of the change

• Adds release-2.1 to the list of target branches for the lightspeed(intelligent-assistant) sync workflow

Which issue(s) does this PR fix or relate to

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

How to test changes / Special notes to the reviewer

Checklist

• For each Chart updated, version bumped in the corresponding Chart.yaml according to Semantic Versioning.
• For each Chart updated, variables are documented in the values.yaml and added to the corresponding README.md. The pre-commit utility can be used to generate the necessary content. Run pre-commit run --all-files to run the hooks and then push any resulting changes. The pre-commit Workflow will enforce this and warn you if needed.
• JSON Schema template updated and re-generated the raw schema via the pre-commit hook.
• Tests pass using the Chart Testing tool and the ct lint command.
• If you updated the orchestrator-infra chart, make sure the versions of the Knative CRDs are aligned with the versions of the CRDs installed by the OpenShift Serverless operators declared in the values.yaml file. See Installing Knative Eventing and Knative Serving CRDs for more details.

[rhdh-qodo-merge]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can turn on the rule miner and Qodo learns your standards from review history

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[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

[Jdubrick]

/cc @rm3l

[rhdh-qodo-merge]

PR Summary by Qodo

ci: sync Lightspeed configs for release-2.1

⚙️ Configuration changes 🕐 Less than 5 minutes

AI Description

• Add release-2.1 to the scheduled and manually triggered Lightspeed configuration sync.
• Reuse the existing workflow to propose upstream config changes on the release branch.

Diagram

graph TD
  A["Scheduled or manual run"] --> B["Branch matrix"] --> C["Sync script"] --> D["Upstream configs"] --> E["Vendored chart"] --> F["Sync PR"]

Loading

High-Level Assessment

Adding the branch to the existing matrix is the simplest approach; the workflow already handles later release branches without separate jobs or scripts.

Files changed (1) +1 / -0

Other (1) +1 / -0

sync-lightspeed-configs.yamlInclude release-2.1 in the Lightspeed sync matrix +1/-0

Include release-2.1 in the Lightspeed sync matrix

• Adds release-2.1 as a workflow matrix target so scheduled and manual runs also check that branch for upstream configuration changes.

.github/workflows/sync-lightspeed-configs.yaml

[rhdh-qodo-merge]

Important

The /generate_labels command by Qodo is sunsetting on the 1st of October 2026 and will no longer be available. We recommend switching to the latest Qodo review capabilities. Learn more