New issue
Advanced search Search tips

Issue 718346 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

no easy way to get around invalid bug= line

Project Member Reported by jochen@chromium.org, May 4 2017

Issue description

when you add a BUG=#somechromiumbug, you'll get the following error on

git cl upload

BUG entry requires issue tracker prefix, e.g. chromium:717906

now the problem is, it doesn't even drop me into the editor, so I can't do much about this :/
 
to clarify, my local git commit message contained the offending bug line
Can't you just amend the commit, change the message and then try again? Doesn't git cl upload present the editor once on initial upload?
I can, but if it doesn't like the CL description, why doesn't it give me the editor?
I'll think about it. On first upload there's maybe a chance, since the remote description doesn't exist yet.
the problem is also that on the first upload when I get the editor, I don't see the warning that the CL description is wrong until after it's too late.
Status: Assigned (was: Assigend)

Sign in to add a comment