Not sure if this is the best way, but it's the simplest way to fix#333.
Everything else is overly complex due to a chicken-egg problem:
Knowing which remote / branch to push involves requires prompting the user,
which requires to have a upstream branch pushed to detect default values.
added this to the v0.7.0 milestone 2 months ago
This is the simplest way to resolve#333. everything else is overly complex:
Knowing which remote / branch to push involves requires prompting, which
requires to have a upstream branch pushed to detect default values.
Note: gh automatically pushes and creates a upstream branch if necessary, which is much better UX.
For tea this is difficult, as we don't know about the intended PR head remote / repo. Maybe we should add DefaultPRHeadRepo to Login config to solve this?
long term we could load the gitea.Repository obj into context ... & check witch permissions we have -> if we dont have push permission check if we own forks if there is > 1 use this as head 🚀