{"action":"closed","issue":{"url":"https://api.github.com/repos/Masterminds/glide/issues/372","repository_url":"https://api.github.com/repos/Masterminds/glide","labels_url":"https://api.github.com/repos/Masterminds/glide/issues/372/labels{/name}","comments_url":"https://api.github.com/repos/Masterminds/glide/issues/372/comments","events_url":"https://api.github.com/repos/Masterminds/glide/issues/372/events","html_url":"https://github.com/Masterminds/glide/issues/372","id":145834564,"number":372,"title":"Proposal: Ability to configure VCS rewrites","user":{"login":"sectioneight","id":97087,"avatar_url":"https://avatars.githubusercontent.com/u/97087?v=3","gravatar_id":"","url":"https://api.github.com/users/sectioneight","html_url":"https://github.com/sectioneight","followers_url":"https://api.github.com/users/sectioneight/followers","following_url":"https://api.github.com/users/sectioneight/following{/other_user}","gists_url":"https://api.github.com/users/sectioneight/gists{/gist_id}","starred_url":"https://api.github.com/users/sectioneight/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sectioneight/subscriptions","organizations_url":"https://api.github.com/users/sectioneight/orgs","repos_url":"https://api.github.com/users/sectioneight/repos","events_url":"https://api.github.com/users/sectioneight/events{/privacy}","received_events_url":"https://api.github.com/users/sectioneight/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-04-04T23:39:56Z","updated_at":"2016-04-05T02:14:26Z","closed_at":"2016-04-05T02:14:26Z","body":"So I realize this is a bit of a special case, but wanted to run by you to see if you'd be open to accepting a PR.\r\n\r\nAt my place of employment, we are switching to Glide (from Godeps). At the same time, we'd like to move away from vendoring. Glide is great for this, and we get reproducible builds **when GitHub is up**, but want to guard against repo renames/GH instability.\r\n\r\nInternally, we have a read-through cache/mirror of GitHub repos, so that if we pull from a special git URI (e.g. `git clone git@mirror:github/Masterminds/glide`) it will read the latest state from GitHub, but still return you the code if GitHub goes down (via gitolite's mirroring options).\r\n\r\nWe'd like the ability to configure glide internally, such that if an engineer adds a github.com dependency to their glide.lock/yaml, it will get pulled through our mirror.\r\n\r\nAlternatively, we are open to patching glide on the client side, such that any \"glide get github.com/...\" will result in the proper VCS settings in glide.yaml. This is slightly less preferable because then we have to distribute a patched glide.\r\n\r\nI'm open to implementing this on an internal fork if you don't foresee others needing this functionality.\r\n\r\nWhat I'm thinking is a `~/.glide.yaml` that has a block like:\r\n```\r\nvcs:\r\n  rewrites:\r\n    from: git@github.com\r\n    to: git@mirror:github/\r\n```\r\n\r\nWhat do you think?"}}