1. Open file you want to edit on GitLab. 2. Wait until all JavaScript bloatware loads. 3. Find out that GitLab logged you out. 4. Press Sign in button. 5. Wait until Cloudflare checks your belonging to human race. 6. Enter credentials. 7. Wait until Cloudflare checks your belonging to human race AGAIN. 8. Edit the file. 9. Fill out PR. 10. Find out that GitLab instead of commiting your changes on top of upstream branch, committed them on top of 3 year old fork master branch, mixing-in some old and unrelated commits to the PR. 11. Remove your fork. 12. Edit the file AGAIN. 13. Fill out PR.
I know GitLab is Microsoft and therefore bad and evil but GitLab isn't any better.
Also I knew I had to do this through CLI, I thought it would be fun to do it slightly unusual way and oh boy it was. :)
@a1ba Also I love how gitlab fucked up the diff at some point on https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/63007 so it tagged all the previously merged MRs. And even as I fixed it right after, the links are still active, so I'm receiving noisy notifications, even today…
@a1ba At least I would say this is worse than the time I accidentally sent like a dozen of emails instead of one because OpenSMTPd sendmail(1) (the de-facto standard command) fails to properly distinguish between a temporary failure and a permanent one. So what I thought wasn't in the queue… in fact was.
@a1ba At least this time the reason it was sent multiple time was between the keyboard and the chair, I should have checked the queue before re-sending.