Branch-format will let you control how branches are named,
which has an effect on when branches collide. This can be
set on cmdline, from config file, or on a topic-by-topic
basis inside the commit text.
user+branch is the default today and will remain the default.
Branch names will never collide if using this, but you cannot
retarget to other base branches, and you must use Uploader: if
another user wants to push to this branch.
user allows retargeting prs to other base branches, but will
not allow multiple base-branches to be specified. if they are,
it will warn to specify user+branch instead.
branch will allow others to upload to the same pr, but uploader:
cannot be used.
none includes both limitations and features of user and branch.
I don't really believe there's good use cases for branch and none,
but i'm implementing them to be complete.
Branch-format will let you control how branches are named, which has an effect on when branches collide. This can be set on cmdline, from config file, or on a topic-by-topic basis inside the commit text.
user+branch is the default today and will remain the default. Branch names will never collide if using this, but you cannot retarget to other base branches, and you must use Uploader: if another user wants to push to this branch.
user allows retargeting prs to other base branches, but will not allow multiple base-branches to be specified. if they are, it will warn to specify user+branch instead.
branch will allow others to upload to the same pr, but uploader: cannot be used.
none includes both limitations and features of user and branch.
I don't really believe there's good use cases for branch and none, but i'm implementing them to be complete.
Fixes: #11