Cool. I have hub installed, I guess I just never used it this way. I'm curious whether the mental overhead of remembering the number and switching applications like that will be the right solution. I do quite like clicking a button, but I'll examine this as an approach.
Now that I'm thinking about it, this might be something I could do entirely in VSCode.
This is what I was going to suggest. I absolutely love this extension for this use case. One of my awesome-* repos used to have merge conflicts with basically every PR because of how I initially structured it (an OSS contributor came and restructured it to make this not happen anymore 💖) and this extension saved so much time when I started using it.
That VS Code plugin could likely do what you need. If it does and that is all you use the Github desktop app for I would say replace it. But, if you like working the other way I would say stick with it. It’s hard to argue with the fact that it works and you get your desired results. I don’t think you should consider your approach “wrong” or “inappropriate” because just like most things with development there is multiple ways to get work done and that’s okay.
I'm an experienced dev specializing in financial and data analysis applications. I've written a lot of Java, SQL, and Matlab. https://numeric-cafe.github.io
Location
Brooklyn, NY
Education
BS in Computer Science
Work
Director, Quantitative Systems at Demex Technologies
I use hub for this too, all the time. You can also just copy and paste the URL to the GitHub PR page and use that instead of the issue number in the hub checkout <whatever> command line.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Cool. I have hub installed, I guess I just never used it this way. I'm curious whether the mental overhead of remembering the number and switching applications like that will be the right solution. I do quite like clicking a button, but I'll examine this as an approach.
Now that I'm thinking about it, this might be something I could do entirely in VSCode.
I just installed this, and I will give it a try:
GitHub Pull Requests for Visual Studio Code
This extension allows you to review and manage GitHub pull requests in Visual Studio Code. The support includes:
Getting Started
It's easy to get started with GitHub Pull Requests for Visual Studio Code. Simply follow these steps to get started.
GitHub Pull Requeststreeview. On the first load, it will appear collapsed…This is what I was going to suggest. I absolutely love this extension for this use case. One of my awesome-* repos used to have merge conflicts with basically every PR because of how I initially structured it (an OSS contributor came and restructured it to make this not happen anymore 💖) and this extension saved so much time when I started using it.
That VS Code plugin could likely do what you need. If it does and that is all you use the Github desktop app for I would say replace it. But, if you like working the other way I would say stick with it. It’s hard to argue with the fact that it works and you get your desired results. I don’t think you should consider your approach “wrong” or “inappropriate” because just like most things with development there is multiple ways to get work done and that’s okay.
I use
hubfor this too, all the time. You can also just copy and paste the URL to the GitHub PR page and use that instead of the issue number in thehub checkout <whatever>command line.