1. 06 Jul, 2018 3 commits
  2. 05 Jul, 2018 8 commits
  3. 04 Jul, 2018 9 commits
  4. 03 Jul, 2018 5 commits
  5. 02 Jul, 2018 2 commits
  6. 29 Jun, 2018 4 commits
    • Imre Farkas's avatar
      Expire correct method caches after HEAD changed · 4cf7a3f773ba
      Imre Farkas authored
      4cf7a3f773ba
    • Grzegorz Bizon's avatar
      Add pipeline stages position clean-up migration · ddbaf9d2f1d6
      Grzegorz Bizon authored
      ddbaf9d2f1d6
    • Sean McGivern's avatar
      Fix MR diffs created with gitaly_diff_between enabled · 8c352331b94c
      Sean McGivern authored
      When we save merge request diffs to the database, we need to expand the diff
      before doing so. That's so that we can expand diffs (within the normal limits)
      without hitting the repository, but just by going to the database.
      
      This is done implicitly - diffs are expanded unless we say otherwise. However,
      we have another option we can pass, that lets us enforce diff size limits, that
      defaults to true.
      
      Prior to this commit:
      
      - The Rugged code path defaulted to setting `expanded: true` and
        `enforce_limits: true`.
      - The Gitaly code path defaulted to setting `expanded: false` and
        `enforce_limits: true`.
      
      This was introduced by b4afa8b098ac, which
      implemented the initial feature. Since then, if the `gitaly_diff_between`
      feature flag was enabled, MRs would have diffs that could not be expanded in
      some cases, with no fix other than to disable the feature flag and force push to
      the MR to refresh the diff in the database.
      8c352331b94c
    • Douwe Maan's avatar
  7. 28 Jun, 2018 5 commits
  8. 27 Jun, 2018 4 commits