frace

That sounds like a good idea. I'll take this on my "consideration list".

@holocronweaver Would you like to pull the "multidomain" branch and test if it gives suitable results? It allows a comma separated list (`service = github.com, gitlab.com`) of domains and checks...

@holocronweaver As an alternative solution I created another branch: https://github.com/frace/git-passport/commits/multidomainsection This would let us do the following: ``` [passport "github, bitbucket, gitlab"] email = ... name = ... [passport "github"]...

@Ferada I don't know if you are using the tool, yet. But which route would you consider to be nicer? Personally I tend to the branch `multidomainsection` since it has...

@tverlaan > I think the naming of a passport should be something given by the user. Eg. work/private/fun/public. Updated #29. I think that'd be fine, too. However it needs to...

@holocronweaver @tverlaan If you don't have any further objections or ideas I will implement the requested features which will lead to a result allowing us to treat our configurations as...

> When I first saw service I thought, "So the URLs are hardcoded for each hosting provider? Like service=github translates to github.com?" The `service` option gets compared with the remote.origin.url...

> BTW, your English is remarkably good for a non-native speaker. Thanks a lot! You'd rather notice it if I'd talk to you in person. :) > I think hosts...

So the newborn's name shall be `url` which gives us the following scheme and possibilities: ``` [passport "whateverUsersWantToPutHereUniquely"] email = ... name = ... url = git-passport,gitlab,http://bitbucket.com,https://github\.(com|org)/frace ``` As long...

That's a good point - and to be honest I didn't think about a scenario where one would remove an early passport entry ^^. So I can't give you an...