BigW Consortium Gitlab

  1. 07 Nov, 2016 2 commits
  2. 04 Nov, 2016 2 commits
  3. 02 Nov, 2016 1 commit
  4. 01 Nov, 2016 2 commits
  5. 31 Oct, 2016 1 commit
  6. 28 Oct, 2016 1 commit
    • Fix lightweight tags not processed correctly by GitTagPushService · fa3bbd44
      Alejandro Rodríguez authored
      When we updated gitlab_git to 10.4.1, `tag.target` changed from pointing
      to the sha of the tag to the sha of the commit the tag points to. The
      problem is that only annotated tags have `object_sha`s, lightweight tags
      don't (it's nil), so (only) in their case we still need to use
      `tag.target`.
  7. 05 Oct, 2016 1 commit
  8. 29 Sep, 2016 2 commits
    • Expose the Koding application settings in the API · 59157c04
      DJ Mountney authored
      This will allow the Koding app to enable the integration itself once is has authorized an admin user using the application secrets.
    • expose pipeline data in builds API · e80e4cb8
      Guilherme Salazar authored
      add pipeline ref, sha, and status to the build API response
      
      add tests of build API (pipeline data)
      
      change API documentation for builds API
      
      log change to builds API in CHANGELOG
      
      CHANGELOG: add reference to pull request and contributor's name
  9. 28 Sep, 2016 1 commit
  10. 27 Sep, 2016 1 commit
  11. 19 Sep, 2016 1 commit
  12. 16 Sep, 2016 1 commit
  13. 15 Sep, 2016 4 commits
  14. 09 Sep, 2016 1 commit
  15. 01 Sep, 2016 1 commit
  16. 31 Aug, 2016 3 commits
  17. 30 Aug, 2016 2 commits
  18. 24 Aug, 2016 3 commits
  19. 23 Aug, 2016 1 commit
  20. 22 Aug, 2016 1 commit
  21. 18 Aug, 2016 6 commits
  22. 16 Aug, 2016 2 commits
    • Improve EE compatibility with protected branch access levels. · 4ddbbcd1
      Timothy Andrew authored
      1. Change a few incorrect `access_level` to `access_levels.first` that
         were missed in e805a647.
      
      2. `API::Entities` can iterate over all access levels instead of just
         the first one. This makes no difference to CE, and makes it more compatible
         with EE.
    • Backport changes from gitlab-org/gitlab-ee!581 to CE. · e805a647
      Timothy Andrew authored
      !581 has a lot of changes that would cause merge conflicts if not
      properly backported to CE. This commit/MR serves as a better
      foundation for gitlab-org/gitlab-ee!581.
      
      = Changes =
      
      1. Move from `has_one {merge,push}_access_level` to `has_many`, with the
         `length` of the association limited to `1`. This is _effectively_ a
         `has_one` association, but should cause less conflicts with EE, which
         is set to `has_many`. This has a number of related changes in the
         views, specs, and factories.
      
      2. Make `gon` variable loading more consistent (with EE!581) in the
         `ProtectedBranchesController`. Also use `::` to prefix the
         `ProtectedBranches` services, because this is required in EE.
      
      3. Extract a `ProtectedBranchAccess` concern from the two access level
         models. This concern only has a single `humanize` method here, but
         will have more methods in EE.
      
      4. Add `form_errors` to the protected branches creation form. This is
         not strictly required for EE compatibility, but was an oversight
         nonetheless.