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

[michael-valdron]

Description

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)

PR acceptance criteria

• Tests
• Documentation

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.

Building Container Images for Testing

Need to test container images from this PR?

For Maintainers: To trigger a test image build, review the code and comment /build-images.
This always builds the HEAD of the PR branch.

For Contributors: Ask a maintainer to run /build-images.

Images will be built and pushed to Quay with links posted in comments.

[rhdh-qodo-merge]

PR Summary by Qodo

Point Intelligent Assistant sync to the migrated config repository

⚙️ Configuration changes 📝 Documentation 🕐 Less than 10 minutes

AI Description

• Redirects Intelligent Assistant config synchronization to the new Red Hat Developer repository.
• Updates maintainer documentation and automated pull-request attribution for the migrated source.
• Keeps the repository transition scoped to upcoming RHDH feature releases.

Diagram

sequenceDiagram
  participant W as Nightly Workflow
  participant S as Sync Script
  participant U as Config Repository
  participant V as Vendored Configs
  W->>S: Run with branch ref
  S->>U: Fetch four files
  U-->>S: Return config content
  S->>V: Replace config blocks

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Branch-aware repository mapping

• ➕ Preserves the legacy repository attribution for RHDH 1.10
• ➕ Supports different upstream repositories across release branches
• ➖ Adds conditional repository mapping to the workflow
• ➖ Duplicates source-selection knowledge already held by each branch's script

2. Expose source metadata from the sync script

• ➕ Makes the script the single source of truth for repository attribution
• ➕ Prevents generated pull-request text from diverging from the actual fetch source
• ➖ Requires a new script output or metadata interface
• ➖ Adds complexity beyond a repository-string migration

Recommendation: The direct script and documentation substitutions are appropriate for upcoming releases. However, the workflow currently targets release-1.10; its generated pull-request link should remain legacy-aware or derive the actual source from the checked-out script so RHDH 1.10 sync PRs are not attributed to the new repository.

Files changed (3) +3 / -3

Documentation (1) +1 / -1

intelligent-assistant.mdDocument the new Intelligent Assistant config source +1/-1

Document the new Intelligent Assistant config source

• Updates maintainer documentation to identify the migrated Red Hat Developer repository as the source of vendored Intelligent Assistant configuration.

docs/intelligent-assistant.md

Other (2) +2 / -2

sync-lightspeed-configs.yamlAttribute automated sync PRs to the migrated repository +1/-1

Attribute automated sync PRs to the migrated repository

• Changes the nightly synchronization pull-request body to link to 'redhat-developer/rhdh-intelligent-assistant-configs' at the selected target branch.

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

sync-lightspeed-configs.shFetch Intelligent Assistant configs from the migrated repository +1/-1

Fetch Intelligent Assistant configs from the migrated repository

• Replaces the upstream GitHub repository identifier used by all four configuration fetches without changing synchronization behavior or file paths.

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. RHDH 1.10 source rerouted ✓ Resolved 🐞 Bug ≡ Correctness

Description

Changing the global UPSTREAM_REPO reroutes the scheduled release-1.10 job to the new repository
because the workflow passes release-1.10 directly as the upstream ref. Nightly updates for the
supported 1.10 release therefore no longer come from its designated legacy repository.

Code

hack/sync-lightspeed-configs.sh[8]

+UPSTREAM_REPO="redhat-developer/rhdh-intelligent-assistant-configs"

Relevance

●●● Strong

The change contradicts the explicit requirement to keep RHDH 1.10 synchronization on the legacy
repository.

PR-#2645

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The workflow matrix contains only release-1.10, checks out that branch, and invokes the script
with --ref release-1.10. The changed global constant is used to construct every GitHub Contents
API request, so the scheduled 1.10 synchronization now necessarily reads
redhat-developer/rhdh-intelligent-assistant-configs@release-1.10.

.github/workflows/sync-lightspeed-configs.yaml[15-18]
.github/workflows/sync-lightspeed-configs.yaml[28-32]
.github/workflows/sync-lightspeed-configs.yaml[49-50]
hack/sync-lightspeed-configs.sh[50-56]
hack/sync-lightspeed-configs.sh[159-162]

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 global upstream repository change causes the existing `release-1.10` nightly job to fetch from the new repository, although RHDH 1.10 must continue using `redhat-ai-dev/lightspeed-configs`.

## Issue Context
The workflow matrix still targets `release-1.10` and passes that value to the script as `--ref`. Introduce release-aware repository selection or move the new repository workflow to the appropriate 2.1 target while preserving the old repository for 1.10. Update the documentation so its release example reflects the supported routing.

## Fix Focus Areas
- hack/sync-lightspeed-configs.sh[8-12]
- .github/workflows/sync-lightspeed-configs.yaml[15-18]
- .github/workflows/sync-lightspeed-configs.yaml[49-50]
- docs/intelligent-assistant.md[147-155]

ⓘ 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

✅ Compliance rules (platform): 18 rules

✅ Cross-repo context — repo relationships

  Explored: repo: redhat-developer/rhdh-plugins (sha: 42ec6574)

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