1. 16 Dec, 2016 1 commit
    • Timothy Andrew's avatar
      Accept environment variables from the `pre-receive` script. · f82d549d
      Timothy Andrew authored
      1. Starting version 2.11, git changed the way the pre-receive flow works.
      
        - Previously, the new potential objects would be added to the main repo. If the
          pre-receive passes, the new objects stay in the repo but are linked up. If
          the pre-receive fails, the new objects stay orphaned in the repo, and are
          cleaned up during the next `git gc`.
      
        - In 2.11, the new potential objects are added to a temporary "alternate object
          directory", that git creates for this purpose. If the pre-receive passes, the
          objects from the alternate object directory are migrated to the main repo. If
          the pre-receive fails the alternate object directory is simply deleted.
      
      2. In our workflow, the pre-recieve script (in `gitlab-shell) calls the
         `/allowed` endpoint, which calls out directly to git to perform
         various checks. These direct calls to git do _not_ have the necessary
         environment variables set which allow access to the "alternate object
         directory" (explained above). Therefore these calls to git are not able to
         access any of the new potential objects to be added during this push.
      
      3. We fix this by accepting the relevant environment variables
         (GIT_ALTERNATE_OBJECT_DIRECTORIES, GIT_OBJECT_DIRECTORY) on the
         `/allowed` endpoint, and then include these environment variables while
         calling out to git.
      
      4. This commit includes (whitelisted) these environment variables while making
         the "force push" check. A `Gitlab::Git::RevList` module is extracted to
         prevent `ForcePush` from being littered with these checks.
      f82d549d
  2. 16 Nov, 2016 1 commit
  3. 28 Oct, 2016 1 commit
  4. 27 Oct, 2016 1 commit
  5. 28 Sep, 2016 1 commit
  6. 19 Sep, 2016 2 commits
  7. 16 Sep, 2016 1 commit
  8. 15 Sep, 2016 7 commits
  9. 01 Sep, 2016 1 commit
  10. 24 Aug, 2016 1 commit
  11. 11 Aug, 2016 1 commit
    • Scott Le's avatar
      api for generating new merge request · 6109daf4
      Scott Le authored
      DRY code + fix rubocop
      
      Add more test cases
      
      Append to changelog
      
      DRY changes list
      
      find_url service for merge_requests
      
      use GET for getting merge request links
      
      remove files
      
      rename to get_url_service
      
      reduce loop
      
      add test case for cross project
      
      refactor tiny thing
      
      update changelog
      6109daf4
  12. 16 Jul, 2016 1 commit
  13. 05 Jul, 2016 1 commit
  14. 30 Jun, 2016 1 commit
  15. 18 Jun, 2016 1 commit
  16. 20 Apr, 2016 1 commit
    • Yorick Peterse's avatar
      Fix setting of "action" for Grape transactions · a257d117
      Yorick Peterse authored
      Merely setting the "action" tag will only result in the transaction
      itself containing a value for this tag. To ensure other metrics also
      contain this tag we must set the action using Transaction#action=
      instead.
      a257d117
  17. 18 Apr, 2016 1 commit
  18. 26 Feb, 2016 1 commit
  19. 24 Feb, 2016 1 commit
  20. 13 May, 2015 1 commit
  21. 24 Mar, 2015 2 commits
  22. 02 Mar, 2015 1 commit
  23. 18 Feb, 2015 2 commits
  24. 07 Feb, 2015 1 commit
  25. 03 Feb, 2015 1 commit
  26. 28 Dec, 2014 1 commit
  27. 01 Dec, 2014 1 commit
  28. 18 Nov, 2014 1 commit
  29. 15 Oct, 2014 1 commit
  30. 07 Oct, 2014 2 commits