1. 15 Dec, 2014 1 commit
  2. 26 Nov, 2014 1 commit
  3. 25 Nov, 2014 2 commits
    • Valery Sizov's avatar
      Merge branch 'require_in_gitlab_net' into 'master' · 6e5c1adc
      Valery Sizov authored
      Add missing 'require_relative' in gitlab_net.rb
      
      Prevent 'uninitialized constant GitlabNet::GitAccessStatus'.
      
      See merge request !49
      6e5c1adc
    • Jacob Vosmaer's avatar
      Add missing 'require_relative' in gitlab_net.rb · 792d686d
      Jacob Vosmaer authored
      Without this 'require' statement, you get the following error:
      
      ```
      $ git ls-remote origin
      /home/git/gitlab-shell/lib/gitlab_net.rb:30:in `check_access':
      uninitialized constant GitlabNet::GitAccessStatus (NameError)
        from /home/git/gitlab-shell/lib/gitlab_shell.rb:63:in `validate_access'
        from /home/git/gitlab-shell/lib/gitlab_shell.rb:24:in `exec'
        from /home/git/gitlab-shell/bin/gitlab-shell:16:in `<main>'
      fatal: Could not read from remote repository.
      
      Please make sure you have the correct access rights
      and the repository exists.
      ```
      792d686d
  4. 24 Nov, 2014 2 commits
  5. 20 Nov, 2014 1 commit
    • Jacob Vosmaer's avatar
      Revert "Merge branch 'git_hook_messages'" · f8453da5
      Jacob Vosmaer authored
      At least the following things were broken:
      - missing require for 'gitlab_access_status' in lib/gitlab_net.rb
      - gitlabhq master internal API returns 'true' or 'false', gitlab-shell
        expects JSON
      
      This reverts commit 11311a95, reversing
      changes made to 45444597.
      f8453da5
  6. 19 Nov, 2014 4 commits
  7. 18 Nov, 2014 4 commits
  8. 17 Nov, 2014 1 commit
  9. 14 Nov, 2014 1 commit
  10. 11 Nov, 2014 1 commit
  11. 07 Nov, 2014 4 commits
  12. 06 Nov, 2014 1 commit
  13. 05 Nov, 2014 1 commit
  14. 31 Oct, 2014 2 commits
  15. 30 Oct, 2014 2 commits
    • jose's avatar
      using true instead of 1 · 7c2208a6
      jose authored
      7c2208a6
    • jose's avatar
      The gitlab pre-receive hook expects the call to exec to return 1 · f25e8e14
      jose authored
      when a user has access. Doing an exit 0 effectively ended the
      thread. No code would be executed after the call to exec.
      
      This changes fixes the problem for the pre-receive hooks but you want
      to check that GitlabAccess.exec is not used elsewhere. A quick
      grep of the code seems to indicate this is not the case
      f25e8e14
  16. 28 Oct, 2014 4 commits
  17. 20 Oct, 2014 4 commits
  18. 16 Oct, 2014 1 commit
  19. 15 Oct, 2014 3 commits