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

.grconfig.json should be in the project folder #8

Open
alexgorbatchev opened this issue Jul 3, 2014 · 5 comments
Open

.grconfig.json should be in the project folder #8

alexgorbatchev opened this issue Jul 3, 2014 · 5 comments

Comments

@alexgorbatchev
Copy link

It's currently not possible to share the .grconfig.json between developers because it contains full paths. Ideally it should be local to the project folder.

@nichtich
Copy link
Contributor

Yes and pathes should be local to the location of .grconfig.json and gr should walk up the directory try to find .grconfig.json with home directory as last choice:

/my/dir/project/.grconfig.json
/my/dir/.grconfig.json
/my/.grconfig.json
/.grconfig.json # maybe skip this as it would be very bad practice
/home/user/.grconfig.json

@nichtich
Copy link
Contributor

Together with #23 one could easily copy .grconfig.json to some location and checkout a bunch of repositories with one command.

@epcim
Copy link

epcim commented Feb 12, 2016

+1
alternatively the "gr" should only work with repos under current $PWD. Force the behaviour by flag "-g" etc..

re: placing it in project repo (ie in root of superrepo) is fine, except you are on path elsewhere (one of the subrepo).

@coderjoe
Copy link
Contributor

I'm not against the idea but it would very much reduce gr's usefulness to me.

@RX14
Copy link

RX14 commented Feb 13, 2016

I think it's possible to have both, and simply extend gr's functionality instead of change it completely.

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

5 participants