<!--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=471056) </details> <!--IssueSummary end--> ### Proposal We are using merge request pipelines to enforce different workflows in our development process (ex. source->target branch, title & desc). At the moment the mr request pipeline already gets rerun when you change the target branch. To prevent that the users needs to rerun it manually or changes for example the title/description after a successful run. It would be great to rerun(optional?) the pipelines also if other properties change. (This was already done for changing the target branch https://gitlab.com/gitlab-org/gitlab/-/merge_requests/107709 https://gitlab.com/gitlab-org/gitlab/-/issues/36995) We would also love to contribute this feature code wise, but we open this issue to get a common consensus on the behaviour.