fix(registry): rename podman gh organization#10288
Conversation
📝 WalkthroughWalkthroughThe Podman backend entry in the registry configuration is updated to reference the new GitHub repository location. The ChangesPodman registry backend update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Greptile SummaryUpdates the podman registry entry to reflect the GitHub organization rename that took effect June 1, 2026, replacing
Confidence Score: 5/5Single-line config update swapping a GitHub org name; the new org is confirmed live and canonical. The change is a one-line update to a registry TOML file. The new GitHub organization (podman-container-tools/podman) exists and hosts the active podman project. No logic, build, or runtime paths are affected. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "fix(registry): rename podman gh organiza..." | Re-trigger Greptile |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@registry/podman.toml`:
- Line 4: The registry entry uses the wrong canonical repo reference: update the
toml key full currently set to "github:podman-container-tools/podman" to
"github:containers/podman" in the podman registry file (the 'full' field) so it
points to the canonical Podman repo; alternatively, if you intend to keep the
podman-container-tools value, add a short justification comment that the
redirect/mirror behavior is intentionally relied upon.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
|
|
||
| [[backends]] | ||
| full = "github:containers/podman" | ||
| full = "github:podman-container-tools/podman" |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Did the Podman GitHub repository move from containers/podman to podman-container-tools/podman in June 2026?
💡 Result:
No, the Podman GitHub repository did not move to podman-container-tools/podman in June 2026. The official GitHub repository for Podman remains at github.com/containers/podman [1][2]. While a new organization named podman-container-tools was established as part of the project's transition to Cloud Native Computing Foundation (CNCF) infrastructure, it serves to house CNCF-related projects and infrastructure rather than replacing the primary containers/podman repository [3]. Discussions within the community identified podman-container-tools as the chosen name for this new organization to facilitate the move of CI infrastructure [3]. Consequently, while some automated processes or related sub-projects may reference the new organization [4], the main Podman codebase continues to be maintained under the containers organization [1][2].
Citations:
- 1: https://github.com/containers/podman?tab=readme-ov-file
- 2: https://github.com/containers/podman/
- 3: CNCF org move, what should the final name be? podman-container-tools/podman#28699
- 4: podman-container-tools/podman@c0f582d
🏁 Script executed:
#!/bin/bash
# Search for any remaining references to containers/podman in the codebase
echo "=== Searching for references to 'containers/podman' ==="
rg -n 'containers/podman' --type-not lock
echo ""
echo "=== Searching for references to 'github.com/containers/podman' ==="
rg -n 'github\.com/containers/podman'Repository: jdx/mise
Length of output: 247
Fix Podman backend full reference in registry/podman.toml
- The canonical Podman GitHub repository is still
github.com/containers/podman;podman-container-toolsis for CNCF/CI-related transition infrastructure, not a replacement repo. - Update line 4 (
full = "github:podman-container-tools/podman") togithub:containers/podman, or explicitly justify that the new reference is supported via redirect/mirror behavior. - Repo search shows no other
containers/podmanreferences, so this change is the likely sole source of mismatch.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@registry/podman.toml` at line 4, The registry entry uses the wrong canonical
repo reference: update the toml key full currently set to
"github:podman-container-tools/podman" to "github:containers/podman" in the
podman registry file (the 'full' field) so it points to the canonical Podman
repo; alternatively, if you intend to keep the podman-container-tools value, add
a short justification comment that the redirect/mirror behavior is intentionally
relied upon.
podman gh org changed names 6/1/26
Summary by CodeRabbit