Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a mv command to move an existing clone to the "correct" path. #1

Closed
jmalloc opened this issue Mar 20, 2017 · 4 comments
Closed

Comments

@jmalloc
Copy link
Owner

jmalloc commented Mar 20, 2017

Not technically blocked, but makes sense to finish #3 first.

  • grit mv - moves the current clone to the standard clone.root location
  • grit mv --golang - equivalent for $GOPATH/src
@jmalloc
Copy link
Owner Author

jmalloc commented Mar 21, 2017

Maybe move --go or similar. FYI @koden-km

@koden-km
Copy link

Yeah move with optional sounds good. Then it can move a cloned repo from anywhere to your "standard" location, which will be good for moving from custom manual clones to grit managed. eg. ~/Documents/Projects/foo to ~/grit/github.com/dudeguy/foo.

@jmalloc
Copy link
Owner Author

jmalloc commented Mar 21, 2017

Yeah that sounds good actually. I'll update the title to match.

@jmalloc jmalloc changed the title Add a go command to move an existing clone to the appropriate $GOPATH Add a move command to move an existing clone to the "correct" path. Mar 21, 2017
@jmalloc jmalloc changed the title Add a move command to move an existing clone to the "correct" path. Add a mv command to move an existing clone to the "correct" path. Mar 22, 2017
@jmalloc
Copy link
Owner Author

jmalloc commented Mar 24, 2017

If there are multiple possible matches, favour the URL from origin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants