<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=14488) </details> <!--IssueSummary end--> When doing difficult refactoring while following good TDD practices, it may be necessary to be sure, that each subsequent commit is under a green bar. However if I rebase a branch, and then force push it to a source branch my MR is created from, I lose build statuses for commits, because commit history had been rewritten. Then, if something got broken during a rebase, which can happen if someone has some conflicts during this process, I will not know, which commit introduced a change that resulted in red bar for all subsequent commits. I'm not sure how to solve this problem, maybe a configuration setting would be a good idea to have, or button to trigger builds for all commit that do not have CI status in MR. What do you think about that @markpundsack @ayufan @tmaczukin?