Midilist and -1

[d.healey]

You can make a new branch based on any commit hash, or just based on Christoph's latests develop branch.

[ustk]

@d-healey Yeah new branch from a specific commit is the way to go. But I have a freakin authentication issue now, the git api messed up the authentication so the Desktop app is blocked too
You'll have to wait for me to fix this then after that I'll make the pull requests

[d.healey]

@ustk

You'll have to wait for me to fix this then after that I'll make the pull requests

No rush. It's always a pain setting up a new workflow like this but once you get it it makes things easier :)

[ustk]

@d-healey That's done :) although because I had n older commit, it is showing up in the pull request. I realized I could even base the new branches on an even older commit but it's too late... It'll be easier next time when my origin will be even with the upstream.

[d.healey]

@ustk My solution is to always branch from Christoph's develop branch, that way it doesn't matter how messed up my own fork is.

[Shannon Burns]

I believe the desktop version may have it as well; I only recently discovered it. Cherry-pick allows you to separate each pull request into its own branch, ensuring that no changes you make are added to the same pull request.

[ustk]

@Shannon-Burns Yes GitHub Desktop has cherry-pick. That's what @d-healey explained to me above about new branches for pull requests that I'd never thought of...