This message was deleted.

Yep, I implemented that when the CLI was still open source. Unfortunately it no longer is. 😞

+1 for this. I have to open the graphite link, menu, copy link to github, paste in a new tab everytime i open a pr right now

@Tommy Kwan you might be interested in https://www.linen.dev/s/graphite/t/12313428/how-do-i-get-from-the-dashboard-to-the-github-view-of-the-pr#8a31cf5c-2074-48eb-8f03-5cd43d31bc7c 🙂

if you want to avoid the menu step, pressing

L G

on the pr page will copy a link to github

I appreciate both of the tips But I don't want to go to graphite to go to github. I just wanna to go from CLI to github PR with no extra steps.

Thanks for the tip, but I don't have gh cli installed and don't want to install it. I just want to use graphite CLI to open the gh PR.

Me too, but we have to wait until they finally hopefully implement it

I use

gh pr view -w

myself when I absolutely need to get to GitHub. We tend to only provide links to GitHub when necessary as a general pattern — this thread has some background on the philosophy: https://www.linen.dev/s/graphite/t/10751389/would-be-nice-to-have-a-fast-way-to-get-from-graphite-review#5a84ace5-68c8-45f9-adf1-8eefefaf3743

I acknowledge the desire to keep gh out of

gt

, but I also think it's important to consider that you frame Graphite as an opt-in tool that doesn't force the whole process on the whole team. Or, more literally: sometimes I still have to work in old-style integration branches and need to get to github to deal with branches merging into those integration branches. I would appreciate being able to have 1 way to open PRs — on graphite or github:

gt pr

or

gt pr --github

I love using

gt

and i just wanna use it more 🙂

I understand and appreciate the desire to have a single tool that allows you to navigate to either — from our perspective it makes sense that the Graphite CLI would link to the PR on Graphite and the GitHub CLI would link to the PR on GitHub — that feels like the right amount of opt-in to us. To draw a more clear model, perhaps it's that the data source is the same, and the workflow tooling leads down divergent paths. I think we want to keep that line as clear as possible — as we are already forced to blur it in other places.

While I'd still appreciate adding a mechanism within

gt pr

to get to my github PR — I think "if you want to use github, you can use

gh

alongside `gt`" is a reasonable response. I'd encourage you to reconsider our request, but can accept that it's not something you're planning to do for the time being 🤷 I appreciate the responses regardless — thanks.

@Tyler Nieman Here's a list of solutions... if you find any others, or make more yourself, feel free to add! https://github.com/benjaffe/graphite-plus-plus