`git cl issue 0` doesn't work with gerrit |
||||
Issue descriptionAffected Version: What steps will reproduce the problem? 1. Upload some branch to gerrit 2. Run `git cl issue 0` to try and clear branch->issue association 3. Run `git cl upload` again What is the expected output? Branch gets uploaded to fresh new issue. What do you see instead? Branch got uploaded to the same issue it was at before I ran `git cl upload 0` Please provide any additional information below.
,
Dec 14 2016
,
Dec 15 2016
I cannot reproduce this bug: $ git cl upload --bypass-hooks --gerrit Using 50% similarity for rename/copy detection. Override with --similarity. AUTHORS | 1 + 1 file changed, 1 insertion(+) remote: Processing changes: new: 1, done remote: remote: New Changes: remote: https://pdfium-review.googlesource.com/2110 DO NOT LAND: add agable to AUTHORS file remote: To https://pdfium.googlesource.com/pdfium * [new branch] 49b9f06401a094ff696e6d023404209834c49c7c -> refs/for/refs/heads/master%m=Initial_upload,notify=NONE $ git cl issue 0 Issue number: None (None) $ git cl upload --bypass-hooks --gerrit Using 50% similarity for rename/copy detection. Override with --similarity. AUTHORS | 1 + 1 file changed, 1 insertion(+) remote: Processing changes: new: 1, done remote: remote: New Changes: remote: https://pdfium-review.googlesource.com/2111 DO NOT LAND: add agable to AUTHORS file remote: To https://pdfium.googlesource.com/pdfium * [new branch] c99928350c4fa33428eb6cff9d3e06bd1d03c840 -> refs/for/refs/heads/master%m=Initial_upload,notify=NONE Please provide a reproduction case.
,
Jan 5 2017
Closing as WontFix because not reproducible. Feel free to reopen if you create a reproduction case.
,
Jan 5 2017
I just tried various repro attempts similar to what I did when this happened, and didn't manage to repro either. I'll shout if I see this again. |
||||
►
Sign in to add a comment |
||||
Comment 1 by andyb...@chromium.org
, Dec 14 2016