1. 15 Apr, 2022 1 commit
  2. 03 Feb, 2022 6 commits
    • Simon Latapie's avatar
      doc: cosmetic refactor · ce56419f
      Simon Latapie authored
      ce56419f
    • Simon Latapie's avatar
    • Simon Latapie's avatar
      ignore upvotes/approval for the "no review" transition · 01eeb753
      Simon Latapie authored
      Fixes #17.
      
      The goal is to avoid upvotes/approval to extend the "no review"
      deadline. This happened when a developer was approving/upvoting a MR:
      - between 0h to 24h before the "no review" deadline (the MR switches from
        "Reviewable" to "Acceptable" and wait 24h after the vote).
      - after the "no review" deadline (the MR switches from "Accepted" to
        "Acceptable" and wait for 24h to go back to its previous state).
      
      Ignoring the presence of votes if there are only upvotes/approvals for
      the "no review" transition should solve both issues without any
      consequence on the other part of the process:
      - if the upvote occurs between 0-48h after the creation of the MR, then
        the "no review" transition will fail during the 0-72h period (deadline
        not reached). During this period, the MR will considered Acceptable,
        then Accepted 24h after the first upvote. After 72h, the "no review"
        transition will succeed no matter what.
      - if the upvote occurs between 48-72h, the "no review" transition will
        fail, MR will be switched to Acceptable. But after 72h, the "no
        review" transition will succeed no matter what, switching MR to
        Accepted.
      - if the upvote occurs after the "no review" deadline, the "no review"
        transition will succeed no matter what, so the MR will be kept as
        Accepted.
      
      Note: all these statements suppose there is no (resolvable/resolved)
      discussion thread opened and/or closed on the MR at all. If this is the
      case, the "no review" transition will fail in any situation, and the
      process will fallback to the previous workflow behavior.
      01eeb753
    • Simon Latapie's avatar
    • Simon Latapie's avatar
      process: speed up additional versions of unreviewed MRs · 694a1620
      Simon Latapie authored
      Fixes #16.
      
      The new "Inactivity" deadline for Developer+ MRs now takes into account
      both the first version of the MR and the last version of it.
      
      With the default threshold values, the goal is to put developer unreviewed MRs
      in Accepted state after the later of 24h after the last non simple change
      (ie fast-forward rebase) and 72h after the MR creation time (or
      out-of-draft time).
      694a1620
    • Simon Latapie's avatar
      api: add first version time function · 31268929
      Simon Latapie authored
      31268929
  3. 28 Jan, 2022 1 commit
  4. 27 Jan, 2022 6 commits
  5. 26 Jan, 2022 1 commit
    • Simon Latapie's avatar
      mr: add a new dev score method (approval) · ccdbc8d1
      Simon Latapie authored
      MR Developer score can now be computed through two different methods:
      - the old one based on the thumbsup/thumbsdown emojis
      - a new one based on the Developers approvals
      
      The bot tries to determine which method should be used to compute the
      vote: if only one method provides a valid score (with a correct update
      time), it is selected. In any other case, the `preferred-score-method`
      parameter is used.
      ccdbc8d1
  6. 14 Jan, 2022 3 commits
  7. 20 Oct, 2021 1 commit
  8. 03 Oct, 2021 1 commit
  9. 03 Jun, 2021 2 commits
  10. 29 Apr, 2021 8 commits
  11. 28 Apr, 2021 4 commits
  12. 27 Apr, 2021 6 commits