Repository navigation
chore(catalog): declare typed relations in catalog-info.yaml - #84
Merged
Merged
Conversation
Each relation to another galax-io repository gets a galaxio.io/uses.<component> or galaxio.io/plans.<component> annotation with its type and how it is used; relations in effect are also in spec.dependsOn, planned ones are not. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jigarkhwar
marked this pull request as ready for review
October 16, 2026 13:50
Contributor
Author
|
Merging on the maintainer's explicit instruction: jigarkhwar (John), 2026-10-16, in the Claude Code chat, after pasting the list of the 20 |
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.
What
Declares how this repository uses the other galax-io repositories, so the Galaxio SDLC agent can tell which repositories a change rolls out to.
Each relation gets one annotation in
metadata.annotations:galaxio.io/uses.<component>: "<type>: <how it is used>"— in effect; the component is also inspec.dependsOn.galaxio.io/plans.<component>: "<type>: <how it will be used>"— planned, no code yet; kept out ofdependsOn.Types:
api,template,contract,runtime,process,docs,target. Annotations rather than newspecfields, because the orchestrator decodesspecwith unknown fields rejected. Contract and the walk that reads it: galax-io/galaxio-sdlc-orchestrator#211 (specs/013-catalog-reverse-impact).Relations in this repository
In effect:
gatling-picatinny—docs: galaxio-gatling plugin teaches agents the Picatinny DSLgatling-kafka-plugin—docs: galaxio-gatling plugin teaches agents the Kafka protocolgatling-jdbc-plugin—docs: galaxio-gatling plugin teaches agents the JDBC protocolgatling-amqp-plugin—docs: galaxio-gatling plugin teaches agents the AMQP protocolspec-kit-galaxio-bootstrap—process: created from the template, takes process updates via copier updatePlanned:
sbt-schema-registry-plugin—docs: skills for Schema Registry in Kafka projectsgalaxio-cli—docs: skills drive scaffolding and run reports through the CLIgalaxio-template-registry—docs: skills pick templates from the registrytemplates-gatling—docs: skills follow the project layout of the templatesdocker-images—docs: skills build and run tests in the CI imagesparsec—docs: skills analyse run results through parsecopennfr—docs: skills write requirements in OpenNFRspec-kit-performance—docs: skills follow the load-testing methodologyOnly
catalog-info.yamlchanges; no build, CI or runtime behaviour changes.🤖 Generated with Claude Code