Add joule-studio and 3 active tutorial groups to repository-groups.json - #24225
Merged
jung-thomas merged 1 commit intoSep 15, 2026
Merged
Conversation
Contributor
|
✅ No issues found Checked a1ff216 • notify-only, does not block merge |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds four repository groups to
config/repository-groups.json:joule-studiodatasphere-skills-clubsap-conversational-aisap-mobile-cardsWhy
The SAGE VS Code authoring extension is moving to discover repository groups dynamically from this file (instead of a list hardcoded in the extension). For that to be a clean, additive change, this config needs to be the single source of truth.
joule-studiois new; the other three already exist assap-tutorials/*repositories and were selectable in the extension's old hardcoded list but absent here — adding them prevents them from disappearing once the extension goes config-driven.Each entry follows the existing schema (
name,description,urlBase,teamAdmin) and includes a human-readable description. Validated as well-formed JSON (25 entries total).