1. 14 Mar, 2016 1 commit
  2. 08 Mar, 2016 1 commit
  3. 03 Mar, 2016 3 commits
  4. 10 Feb, 2016 5 commits
  5. 09 Feb, 2016 7 commits
  6. 05 Jan, 2016 1 commit
  7. 04 Jan, 2016 2 commits
  8. 14 Dec, 2015 2 commits
  9. 11 Dec, 2015 2 commits
  10. 01 Dec, 2015 1 commit
  11. 26 Nov, 2015 1 commit
  12. 25 Nov, 2015 8 commits
  13. 24 Nov, 2015 1 commit
    • Kirill Smelkov's avatar
      Pass $HOME to git as well · 9e087f64
      Kirill Smelkov authored
      [ this patch has the same rationale and reasoning as
        https://gitlab.com/gitlab-org/gitlab-workhorse/commit/0d0bd209
      
        details follow ]
      
      Git has 3 places for configs:
      
          - system
          - global (per user), and
          - local  (per repository)
      
      System config location is hardcoded at git compile time (to usually
      $prefix/etc/gitconfig). Local configuration is usually picked because we
      pass full repo path to subcommand. But global configuration is currently not
      picked at all, because HOME env variable is not passed to git.
      
      Pass $HOME through and let git see it's "global" config.
      
      Currently GitLab omnibus stores gitlab user name/email  + "autocrlf =
      true" in global config, so missing it should not be a blocker for
      receive/send-pack operations. But having it is more correct and can be
      handy in the future if/when more git operations are done from-under
      gitlab-shell.
      
      Having $HOME properly set is also needed when one cannot change system
      git config and have to put site-wide configuration into global git
      config under $HOME.
      
      That was the case I've hit and the reason for this patch.
      9e087f64
  14. 19 Nov, 2015 1 commit
  15. 18 Nov, 2015 1 commit
  16. 17 Nov, 2015 2 commits
  17. 12 Nov, 2015 1 commit