• Martin@feddit.nu
    link
    fedilink
    arrow-up
    4
    ·
    2 years ago

    We decided that everyone in the team is allowed to approve changes. If no one has reviewed your change within 24 hours you are allowed to approve it yourself. It will usually come up in the daily sync that a self approval is imminent, which usually leads to someone taking a look.

    • PowerCrazy@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 years ago

      Self-approval leads to a road of sadness. For example, a theoretical company needs to self-renew an ssl cert. No problem, the cert will be stored with the rest of the secrets and retrieved in a secure way on deployment. Unfortunately if you don’t store the cert key in a secure way, the deployment still works fine and you don’t need to figure out the “onerous” encryption process.

      So you push the private key to the company git repo, and then deploy the cert! Done and Done.

    • Doc Avid Mornington@midwest.social
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 years ago

      which usually leads to someone taking a look

      Nevermind the idea that one reviewer is somehow sufficient, this sounds like pure fantasy. Did you forget a “/s”?

      • Martin@feddit.nu
        link
        fedilink
        arrow-up
        1
        ·
        2 years ago

        Who said anything about only requiring 1 reviewer? And no, I did not drop an /s. You should try working for a healthy team where everyone takes collective responsibility and where the teams progress is more important than any one person’s progress.