Point the KSA remotes at the KSP-CKAN org#5
Merged
Conversation
- prod-stack.py netkan/ckanmeta remotes move to KSP-CKAN, matching the global NETKAN_USER/CKANMETA_USER so staged and SpaceDock PRs resolve - Merge only at/after the repo transfer
Maximilian-Nesslauer
added
the
infrastructure
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
1 participant
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.
Flips the ksa netkan/ckanmeta remotes in prod-stack.py to KSP-CKAN, matching the global NETKAN_USER/CKANMETA_USER. This retires the staged/SpaceDock-PR caveat documented in #3.
Do not merge before the repo transfer.
Part of KSP-CKAN/CKAN#4457.