BigW Consortium Gitlab

  1. 15 Dec, 2016 1 commit
  2. 11 Dec, 2016 2 commits
  3. 09 Dec, 2016 1 commit
  4. 08 Dec, 2016 1 commit
  5. 07 Dec, 2016 1 commit
  6. 06 Dec, 2016 3 commits
  7. 02 Dec, 2016 2 commits
  8. 29 Nov, 2016 1 commit
  9. 23 Nov, 2016 1 commit
  10. 21 Nov, 2016 1 commit
  11. 19 Nov, 2016 2 commits
  12. 18 Nov, 2016 1 commit
  13. 17 Nov, 2016 5 commits
  14. 09 Nov, 2016 1 commit
  15. 07 Nov, 2016 2 commits
  16. 01 Nov, 2016 1 commit
  17. 28 Oct, 2016 2 commits
  18. 24 Oct, 2016 2 commits
    • Implement review comments from @DouweM. · b803bc7b
      Timothy Andrew authored
    • Fix branch protection API. · f79f3a1d
      Timothy Andrew authored
      1. Previously, we were not removing existing access levels before
         creating new ones. This is not a problem for EE, but _is_ for CE,
         since we restrict the number of access levels in CE to 1.
      
      2. The correct approach is:
      
          CE -> delete all access levels before updating a protected branch
          EE -> delete developer access levels if "developers_can_{merge,push}" is switched off
      
      3. The dispatch is performed by checking if a "length: 1" validation is
         present on the access levels or not.
      
      4. Another source of problems was that we didn't put multiple queries in
         a transaction. If the `destroy_all` passes, but the `update` fails,
         we should have a rollback.
      
      5. Modifying the API to provide users direct access to CRUD access
         levels will make things a lot simpler.
      
      6. Create `create/update` services separately for this API, which
         perform the necessary data translation, before calling the regular
         `create/update` services. The translation code was getting too large
         for the API endpoint itself, so this move makes sense.
  19. 20 Oct, 2016 1 commit
    • Differentiate the expire from leave event · 9124310f
      Callum Dryden authored
      At the moment we cannot see weather a user left a project due to their
      membership expiring of if they themselves opted to leave the project.
      This adds a new event type that allows us to make this differentiation.
      Note that is not really feasable to go back and reliably fix up the
      previous events. As a result the events for previous expire removals
      will remain the same however events of this nature going forward will be
      correctly represented.
  20. 19 Oct, 2016 8 commits
  21. 18 Oct, 2016 1 commit