BED-9542: fix ghcr creds - #209
Conversation
The package was using a custom user and token (set in repo secrets) to push to ghcr. now that we're pushing this image to the same org (and not the old org) we can use the default wokflow token. ref: BED-9542
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. WalkthroughThe build and publish workflows now authenticate Docker with GHCR using ChangesContainer authentication
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This PR switches image publishing to the repository’s default workflow token for the same organization. No actionable merge-blocking risk remains. Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
The package was using a custom user and token (set in repo secrets) to push to ghcr. now that we're pushing this image to the same org (and not the old org) we can use the default wokflow token.
ref: BED-9542
Summary by CodeRabbit