Rename pelican-dev org references to pelican - #208
Merged
notAreYouScared merged 1 commit intoAug 16, 2026
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Everything left after the module rename: the --repo-owner default that self-update uses to find releases, the CODEOWNERS team, the image in the compose example, and the links in the README, SECURITY and CHANGELOG.
lancepioch
force-pushed
the
chore/org-rename-pelican
branch
from
August 14, 2026 23:34
779980a to
96636e9
Compare
notAreYouScared
marked this pull request as ready for review
August 16, 2026 21:16
This was referenced Aug 16, 2026
lancepioch
added a commit
that referenced
this pull request
Aug 16, 2026
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
2 participants
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.
Do not merge this yet. This is the half that genuinely has to wait, unlike #209.
The module path rename moved out into #209, which is safe to land whenever, so what's left here is just the six lines that are live values pointing at a place that doesn't exist yet. Based on #209 for now so the diff only shows the remainder; it'll retarget itself to main once that one goes in.
The one worth actually looking at is
cmd/selfupdate.go, where--repo-ownerdefaults topelican-dev. That's the value self-update uses to go looking for releases, and it's baked into binaries that are already out in the wild, so a fresh checkout doesn't help anybody who already has wings installed.The rest is the CODEOWNERS team, the image in
docker-compose.example.yml, and links in the README, SECURITY and CHANGELOG.Two things that can't be done from a PR and still need doing separately: recreate the
@pelican/wingsteam so CODEOWNERS resolves again, and republish the wings image underghcr.io/pelican/wings.