Closed twouters closed 2 years ago
Thanks for the well-written bug report and I can understand your pain :)
ISTR we do save buffer output on errors with 'lab edit'. I think this should be possible to do with 'lab create'.
I'll look into this.
@twouters would be it be better to create the MR, and then write an error message to the console indicating that the user could not be found?
@twouters would be it be better to create the MR, and then write an error message to the console indicating that the user could not be found?
Maybe also mention that the assignee can be changed with lab mr edit <id> --assign <user>
? (filling in the MR ID, and maybe the (wrong) username)
I'm fine with that, if the buffer output is saved and can be restored I just figured you mean to actually create the MR in gitlab, that sounds even better.
lab mr create -a <username>
throws a segmentation fault when a username doesn't exist on a gitlab instance (because of typo's or just forgetting the actual username or whatever).This is especially annoying because I usually run into this after writing lengthy MR descriptions and have to start typing it all over again.
Could it be changed to first check if users actually exist before initiating the editor to edit MERGEREQ_EDITMSG, or catch these (or similar) errors and save/cache the submitted MR description somewhere so that it can be retried?