BigW Consortium Gitlab

  1. 09 Dec, 2016 2 commits
  2. 05 Dec, 2016 1 commit
    • Feature: delegate all open discussions to Issue · 1123057a
      Bob Van Landuyt authored
      When a merge request can only be merged when all discussions are
      resolved. This feature allows to easily delegate those discussions to a
      new issue, while marking them as resolved in the merge request.
      
      The user is presented with a new issue, prepared with mentions of all
      unresolved discussions, including the first unresolved note of the
      discussion, time and link to the note.
      
      When the issue is created, the discussions in the merge request will get
      a system note directing the user to the newly created issue.
  3. 02 Dec, 2016 1 commit
  4. 01 Dec, 2016 1 commit
  5. 29 Nov, 2016 1 commit
  6. 28 Nov, 2016 1 commit
  7. 23 Nov, 2016 2 commits
    • Remove event caching code · 5371da34
      Yorick Peterse authored
      Flushing the events cache worked by updating a recent number of rows in
      the "events" table. This has the result that on PostgreSQL a lot of dead
      tuples are produced on a regular basis. This in turn means that
      PostgreSQL will spend considerable amounts of time vacuuming this table.
      This in turn can lead to an increase of database load.
      
      For GitLab.com we measured the impact of not using events caching and
      found no measurable increase in response timings. Meanwhile not flushing
      the events cache lead to the "events" table having no more dead tuples
      as now rows are only inserted into this table.
      
      As a result of this we are hereby removing events caching as it does not
      appear to help and only increases database load.
      
      For more information see the following comment:
      https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037
  8. 21 Nov, 2016 1 commit
  9. 17 Nov, 2016 2 commits
  10. 09 Nov, 2016 1 commit
  11. 04 Nov, 2016 1 commit
  12. 03 Nov, 2016 1 commit
  13. 28 Oct, 2016 1 commit
  14. 24 Oct, 2016 1 commit
  15. 20 Oct, 2016 3 commits
  16. 19 Oct, 2016 1 commit
  17. 18 Oct, 2016 3 commits
  18. 14 Oct, 2016 5 commits
  19. 13 Oct, 2016 1 commit
    • Allow setting content for resolutions · 3f71c43e
      Sean McGivern authored
      When reading conflicts:
      
      1. Add a `type` field. `text` works as before, and has `sections`;
         `text-editor` is a file with ambiguous conflict markers that can only
         be resolved in an editor.
      2. Add a `content_path` field pointing to a JSON representation of the
         file's content for a single file.
      3. Hitting `content_path` returns a similar datastructure to the `file`,
         but without the `content_path` and `sections` fields, and with a
         `content` field containing the full contents of the file (with
         conflict markers).
      
      When writing conflicts:
      
      1. Instead of `sections` being at the top level, they are now in a
         `files` array. This matches the read format better.
      2. The `files` array contains file hashes, each of which must contain:
         a. `new_path`
         b. `old_path`
         c. EITHER `sections` (which works as before) or `content` (with the
            full content of the resolved file).
  20. 06 Oct, 2016 1 commit
  21. 03 Oct, 2016 2 commits
  22. 27 Sep, 2016 1 commit
  23. 21 Sep, 2016 2 commits
  24. 20 Sep, 2016 4 commits
    • Use the `IssuableBaseService` lifecycle hooks to cache `MergeRequestsClosingIssues` · 68e1b5bb
      Timothy Andrew authored
      - Instead of overriding `create` and `update` in `MergeRequests::BaseService`
      - Get all merge request service specs passing
    • Implement a second round of review comments from @DouweM. · 918e589c
      Timothy Andrew authored
      - Don't use `TableReferences` - using `.arel_table` is shorter!
      - Move some database-related code to `Gitlab::Database`
      - Remove the `MergeRequest#issues_closed` and
        `Issue#closed_by_merge_requests`  associations. They were either
        shadowing or were too similar to existing methods. They are not being
        used anywhere, so it's better to remove them to reduce confusion.
      - Use Rails 3-style validations
      - Index for `MergeRequest::Metrics#first_deployed_to_production_at`
      - Only include `CycleAnalyticsHelpers::TestGeneration` for specs that
        need it.
      - Other minor refactorings.
    • Implement (some) comments from @DouweM's review. · 71d4bf72
      Timothy Andrew authored
      - Move things common to `Issue` and `MergeRequest` into `Issuable`
      - Move more database-specific functions into `Gitlab::Database`
      - Indentation changes and other minor refactorings.
    • If merge request wasn't persisted yet, we show only 1 pipeline: · 3ae99b2c
      Lin Jen-Shin authored
      However, if MergeRequest#all_commits_sha would want to handle
      non-persisted merge request, by judging its name, it should not
      just give 1 SHA, but all of them.
      
      But we don't really care all_commits_sha for non-persisted merge
      request anyway. So I think we should just ignore that case.
      
      Better to not implementing something than implementing it in a
      wrong and confusing way.