You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature or problem you’d like to solve
In the default setting one needs to omit pr, which is confusing (because it is not consistent why one needs to write checkout in one place and co in another place although both terms have the same effect)
$ gh pr co 13280
unknown command"co"for"gh pr"
$ gh co 13280
remote: Enumerating objects: 178, done.
Thank you for your issue! We have categorized it as a feature request, and it has been added to our backlog. In doing so, we are not committing to implementing this feature at this time, but, we will consider it for future releases based on community feedback and our own product roadmap.
Unless you see the
help wantedContributions welcome
label, we are not currently looking for external contributions for this feature.
If you come across this issue and would like to see it implemented, please add a thumbs up! This will help us prioritize the feature. Please only comment if you have additional information or viewpoints to contribute.
Since the gh co is already a default alias (and is the only one), I don't see any harm in having pr co.
Warning
A bit unrelated, but users should beware of using gh co as explained in #4789 (comment), mostly because it's not a really hard-coded alias and it can get deleted or reassigned by the user.
Since the gh co is already a default alias (and is the only one), I don't see any harm in having pr co.
Warning
A bit unrelated, but users should beware of using gh co as explained in #4789 (comment), mostly because it's not a really hard-coded alias and it can get deleted or reassigned by the user.
@babakks I think I'd prefer we add a real Cobra alias to the pr checkout subcommand so gh pr co is natively supported instead of it being a default gh alias.
It would be scoped to the pr command set, so there's no risk of collision with extensions and whatnot. I don't think it makes sense to make it a default gh alias over a real Cobra alias, personally.
Activity
github-actions commentedon Aug 27, 2025
Thank you for your issue! We have categorized it as a feature request, and it has been added to our backlog. In doing so, we are not committing to implementing this feature at this time, but, we will consider it for future releases based on community feedback and our own product roadmap.
Unless you see the help wantedContributions welcome
label, we are not currently looking for external contributions for this feature.
If you come across this issue and would like to see it implemented, please add a thumbs up! This will help us prioritize the feature. Please only comment if you have additional information or viewpoints to contribute.
babakks commentedon Aug 27, 2025
Hi @koppor, And thanks for the issue! 🙏
Since the
gh cois already a default alias (and is the only one), I don't see any harm in havingpr co.Warning
A bit unrelated, but users should beware of using
gh coas explained in #4789 (comment), mostly because it's not a really hard-coded alias and it can get deleted or reassigned by the user.WDYT, @BagToad?
[-]Consisnt aliases: `gh co` and `gh pr co`[/-][+]Consistent aliases: `gh co` and `gh pr co`[/+]BagToad commentedon Sep 2, 2025
@babakks I think I'd prefer we add a real Cobra alias to the
pr checkoutsubcommand sogh pr cois natively supported instead of it being a defaultghalias.It would be scoped to the
prcommand set, so there's no risk of collision with extensions and whatnot. I don't think it makes sense to make it a defaultghalias over a real Cobra alias, personally.babakks commentedon Sep 24, 2025
@BagToad Oh, yes, Definitely.