3 ms·

I've tried that as well. For me it was really difficult as I use the current changes quite a lot, and it makes it a lot more difficult to grasp the work I've do

I've tried that as well. For me it was really difficult as I use the current changes quite a lot, and it makes it a lot more difficult to grasp the work I've done so far without having a meaningful change set.

genuine_smiles 5y ago
I keep a draft PR open to keep track of this. Not has nice as vs-codes diff tool though.
- ianjsikes 5y ago
  You can still use VS Code's diff if you have the GitHub Pull Requests extension: https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github https://marketplace.visualstudio.com/items?itemName=GitHub.v...
  - Larrikin 5y ago
    Anything that would allow a similar workflow in JetBrains IDEs?
chayleaf 5y ago
you can use separate dev/release branches, and do something like "git diff master" (if you dont git push, you don't even need a separate branch, git diff origin/master works, but you lose half the point of frequent commits then)