• Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False

      thinking up a solution to no_qe PR reviews.

      my feeling is 3 approvers for any PR creates unnecessary drag & red tape.
      i'm looking into the option of creating a GH-bot that automatically approves PRs, that could be used in place of a 3rd reviewer, in appropriate PRs (hey, we can even call it "no_qe"!).

      pinging QE for a rubber stamp approval for no_qe PRs can be problematic in two ways: it creates extra overhead on a team that's already overflowing (QE), and is inapplicable for small tasks that don't have jira tickets.

      found resources:

      another idea is to create a rule for having 2 reviewers on "no QE" branches, but that seems impossible. we can look into it more deeply to verify that first.

              Unassigned Unassigned
              emalka@redhat.com Lyn M
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: