Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • G gitlab-shell
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedinexedi
  • gitlab-shell
  • Repository
  • gitlab-shell
  • lib
  • gitlab_shell.rb
Find file BlameHistoryPermalink
  • Zeger-Jan van de Weg's avatar
    Clean up cmd_exec execution environment · 911e49e1
    Zeger-Jan van de Weg authored Aug 16, 2018
    Given the gitaly-* now proxy the data from the client to the Gitaly
    server, the environment variables aren't used. Therefor we don't have to
    set them either. Only exception to the rule, is the GITALY_TOKEN.
    
    These changes also remove the `GIT_TRACE` options, introduced by
    192e2bd3.
    
    Part of: https://gitlab.com/gitlab-org/gitaly/issues/1300
    911e49e1
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7