Feature Request P3
Status Update
Comments
ek...@google.com <ek...@google.com> #2
[Empty comment from Monorail migration]
ek...@google.com <ek...@google.com> #3
[Monorail components: -repo]
so...@google.com <so...@google.com> #4
[Empty comment from Monorail migration]
ar...@google.com <ar...@google.com> #5
Is this still an issue? It seems like this is how the current behavior works.
```
# there are two branches to push; foo and bar.
$ repo upload
// opens editor
$ repo upload --br=foo
Upload project depot/ to remote branch refs/heads/main:
branch foo ( 1 commit, Wed Mar 22 22:04:40 2023 +0000):
7eedb479 foo
tohttps://chromium-review.googlesource.com (y/N)? y
...
```
```
# there are two branches to push; foo and bar.
$ repo upload
// opens editor
$ repo upload --br=foo
Upload project depot/ to remote branch refs/heads/main:
branch foo ( 1 commit, Wed Mar 22 22:04:40 2023 +0000):
7eedb479 foo
to
...
```
ar...@google.com <ar...@google.com>
ca...@google.com <ca...@google.com> #6
The issue is when you have one branch in multiple project:
cd project1; repo start foo; ... git commit ...; cd project2; repo start foo;... git commit ...; repo upload --cbr ;
va...@google.com <va...@google.com> #7
the code that controls this prompting logic hasn't changed since originally reported
Description
however, if the user specifies an explicit branch, we should switch to just printing a summary in the terminal and prompting them to confirm if they want to continue.