Clarify unverified GPG Keys in Merge Requests

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

• Close this issue

Problem to solve

When viewing changes in a Merge Request, a verified commit signature clearly states why a key has been verified, but lacks a justification for unverified

Screenshots

Verified	Unverified

Proposal

Scenarios

  enum verification_status: {
    unverified: 0,
    verified: 1,
    same_user_different_email: 2,
    other_user: 3,
    unverified_key: 4,
    unknown_key: 5
  }