don't push before creating a pull #334

Merged
6543 merged 3 commits from noerw/tea:fix-333-pr-create-push into master 2021-03-05 10:27:10 +00:00
Member

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.

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.
noerw added this to the v0.7.0 milestone 2021-03-04 18:18:34 +00:00
noerw added the
kind/bug
label 2021-03-04 18:18:34 +00:00
noerw added 1 commit 2021-03-04 18:18:35 +00:00
don't push before creating a pull
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.
All checks were successful
continuous-integration/drone/pr Build is passing
5df68437ba
6543 added 1 commit 2021-03-05 08:57:57 +00:00
Merge branch 'master' into fix-333-pr-create-push
All checks were successful
continuous-integration/drone/pr Build is passing
0520efa9d5
Author
Member

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?

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?
Owner

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 ?

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 ?
6543 added 1 commit 2021-03-05 10:07:11 +00:00
Merge branch 'master' into fix-333-pr-create-push
All checks were successful
continuous-integration/drone/pr Build is passing
1bf61a369e
6543 approved these changes 2021-03-05 10:07:26 +00:00
Dismissed
zeripath approved these changes 2021-03-05 10:14:53 +00:00
Dismissed
khmarbaise approved these changes 2021-03-05 10:16:02 +00:00
Dismissed
6543 merged commit d474883e90 into master 2021-03-05 10:27:09 +00:00
6543 deleted branch fix-333-pr-create-push 2021-03-05 10:27:16 +00:00
Sign in to join this conversation.
No description provided.