Verified commits lose verification on rebase

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem to solve

When rebasing with GitLab (such as using /rebase or fast-forward merge trains), verified commits lose their verification status. But such commits have only been handled by GitLab and should generally be trustworthy.

Proposal

Introduce a mechanism to re-verify verified commits on rebase. These commits should show up as either

  • "Verified" with a hover clarification that it is a commit re-verified by GitLab
  • "Re-verified" with the same clarification
Edited by 🤖 GitLab Bot 🤖