If the user mistakenly creates a Backport PR with the wrong hash and then later corrects it, the clean status is never correctly re-evaluated. It gets stuck only considering the very first Backport hash that was added. The clean status should re-evaluate on the last/current Backport hash.

Further, on Gitlab, if the user tries to manually label the MR as clean, it's highly likely that the user will use the Gitllab /label command instead of the Skara /clean command. If this happens, Skara will not detect that a user set the label and will just immediately remove it again. The Skara /clean command was broken until recently SKARA-1242. When fixing that bug, I also updated the documentation for the /clean command, which should reduce some of the confusion and at least provide a reasonable workaround.