guyzmo
@dmerejkowsky you're not helping ☺ @graingert I bought https://git-repo.org though we'll need to make a nice page
@graingert hosting is not an issue (I'm covered here) but doing a webpage (beyond the README file) is not my priority… adding more features, and a better documentation is.
@guyhughes I know and I don't really care because there's no real name conflict (google's tool really is named `repo` everywhere, and only in a few places `git-repo`). So this...
I guess I'll just flip a coin for a name change when it will be time to start working on 2.0. Until then, let's keep on working on implementations! For...
Thank you for the suggestion! 👍 It's definitely a good alternative to the only other realistic name suggested here. I have to admit that the name `git-services` is growing on...
oops, @metasean, thanks for the note 😇 fixing those
as a note: only the config wizard does not work, the tool does work! At the end of [the configuration section](https://github.com/guyzmo/git-repo#configuration), it is explained how you can extract your git-repo...
well, the issue is still painful and there's a tracking issue on gitpython. I guess I could add take the reference to the config file that needs to be modified?
though that comment was for whoever popped on the #git-repo channel asking on how he can use a versioned git config, citing this issue... 😉
Ah! That I did not went through. Even though that exact issue is painful, the lack of documentation is definitely an urgent thing, including a manpage. cf #146 for that...