chore(intelligent-assistant): change intelligent assistant (lightspeed) configs repository

[michael-valdron]

Description of the change

We have migrated redhat-ai-dev/lightspeed-configs to redhat-developer/rhdh-intelligent-assistant-configs for all upcoming feature releases of RHDH. Starting with RHDH 2.1, the intelligent assistant (lightspeed) configs will be fetched from redhat-developer/rhdh-intelligent-assistant-configs.

Note: redhat-ai-dev/lightspeed-configs will be kept active for RHDH 1.10 support, do not backport this change.

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

https://redhat.atlassian.net/browse/RHIDP-14891 (Developer Week)

How to test changes / Special notes to the reviewer

Run bash hack/sync-lightspeed-configs.sh to test syncing the content. Changes from this script are not part of this PR's scope however.

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]

PR Summary by Qodo

Migrate Lightspeed sync to the RHDH intelligent assistant repository

⚙️ Configuration changes 📝 Documentation 🕐 Less than 10 minutes

AI Description

• Switches default Lightspeed synchronization to the RHDH intelligent assistant configuration
 repository.
• Aligns nightly sync PR messaging and contributor documentation with the migrated source.
• Keeps synchronization behavior and the configurable repository override unchanged.

Diagram

graph TD
  W["Nightly workflow"] -->|"runs"| S["Sync script"] -->|"fetches"| U(["New config repo"])
  S -->|"vendors"| V["Chart configs"]
  D["Contributor guide"] -->|"documents"| S

Loading

High-Level Assessment

Directly replacing the canonical repository in the script and its user-facing references is the simplest appropriate approach. Centralizing the URL across shell, workflow, and Markdown was considered, but would add unnecessary indirection for three distinct contexts while the script already supports explicit repository overrides.

Files changed (3) +3 / -3

Documentation (1) +1 / -1

CONTRIBUTING.mdDocument the new Lightspeed configuration source +1/-1

Document the new Lightspeed configuration source

• Updates contributor guidance to identify the migrated repository as the upstream source for vendored intelligent assistant configuration files.

CONTRIBUTING.md

Other (2) +2 / -2

sync-lightspeed-configs.yamlReference the migrated repository in automated sync pull requests +1/-1

Reference the migrated repository in automated sync pull requests

• Updates the nightly workflow's generated pull request body to identify and link the new intelligent assistant configuration repository.

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

sync-lightspeed-configs.shUse the migrated repository as the default sync source +1/-1

Use the migrated repository as the default sync source

• Changes the script's default GitHub repository to redhat-developer/rhdh-intelligent-assistant-configs. Existing ref selection, check mode, and explicit repository overrides remain unchanged.

hack/sync-lightspeed-configs.sh

[rhdh-qodo-merge]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Sync PR misstates source ✓ Resolved 🐞 Bug ≡ Correctness

Description

The workflow claims release-1.10 sync changes came from the new intelligent-assistant repository,
even though it checks out release-1.10 before running that branch's legacy sync script. Generated
PRs therefore link reviewers to the wrong upstream changes.

Code

.github/workflows/sync-lightspeed-configs.yaml[151]

+          Automated nightly sync of Lightspeed Core config files from [redhat-developer/rhdh-intelligent-assistant-configs @ ${TARGET_BRANCH}](https://github.com/redhat-developer/rhdh-intelligent-assistant-configs/tree/${TARGET_BRANCH}).

Relevance

●●● Strong

The release-1.10 job runs the legacy sync script, so its generated PR description names the wrong
upstream source.

PR-#480
PR-#200

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The matrix targets only release-1.10, and the workflow checks out that branch before invoking
hack/sync-lightspeed-configs.sh; consequently, the main-branch default repository changed by this
PR is not the script version executed by this job. The newly hardcoded PR body nevertheless
identifies the new repository as its source.

.github/workflows/sync-lightspeed-configs.yaml[13-18]
.github/workflows/sync-lightspeed-configs.yaml[28-39]
.github/workflows/sync-lightspeed-configs.yaml[80-81]
.github/workflows/sync-lightspeed-configs.yaml[148-156]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The nightly release-1.10 sync PR body incorrectly attributes synced files to `redhat-developer/rhdh-intelligent-assistant-configs`. The job checks out release-1.10 and executes its sync script, so the PR body must identify the legacy `redhat-ai-dev/lightspeed-configs` source.

## Issue Context
The workflow matrix currently contains only `release-1.10`. Restore the legacy repository in the generated body, or derive the displayed repository from the same branch-aware configuration used by the sync operation.

## Fix Focus Areas
- .github/workflows/sync-lightspeed-configs.yaml[151-151]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Context sources

⚠️ Tickets: not configured — ticket URL found in PR but could not be fetched — check ticket provider credentials

✅ Cross-repo context — repo relationships

Tip of the day

💡 Did you know, you can add REVIEW.md to your repo root and Qodo follows it on every PR

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