Finish the wings org rename (the part #208 missed) - #211
Conversation
Nothing outside this repo imports wings, so the imports are all self-referential and this builds the same either way; the point is just to have the module path match where the code lives. The version stamping has to agree with the module path or it silently stops working, so SRC_PATH, the release ldflags, the Dockerfile and the Makefile move in the same commit.
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.
|
Wrong base — this replays the module rename that's already on main. Redoing it as a clean branch off current main. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (98)
📝 WalkthroughWalkthroughThe pull request renames the Go module and repository references from ChangesModule path migration
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
#208 never actually reached main. It was based on
chore/wings-module-pathwhile that was still open, and because that branch didn't get deleted after #209 merged, GitHub left the base alone and #208 merged into the branch instead of into main. So the module rename landed and these six lines didn't.This is the same content, retargeted at main. Nothing new in it.
The one that matters is
cmd/selfupdate.go, where--repo-owneris stillpelican-dev— that's what self-update uses to look for releases. The rest is the CODEOWNERS team, the image indocker-compose.example.yml, and links in the README, SECURITY and CHANGELOG.Summary by CodeRabbit