might need to write some tests for those?

Oh yes please ! It should be relatively straightforward to deduce how to write tests for this by looking at the existing ones. Usually there are helper functions to setup even more complex fixtures.

Before I forget, could you also look at how existing methods are documented and match the documentation style ? This would include documenting all parameters, for example.

I might, but sadly I'm now in the train, going away for four days, during which I'm on a crappy tablet on which I cannot work. Though, I very much would like to see this new methods included in the next patchset so I can remove the monkey patching from my own codebase as well :-)

cfhttps://github.com/guyzmo/git-repo/blob/master/git_repo/services/service.py#L25-43

So, I've squashed my commit with a new one, featuring a few changes:

• Theset_url method is a direct wrapper forgit remote set-url ;
• theurls property is providing an iterator over the remote's URLs (I followed how you namedrefs)

Then I've added a couple of convenience methods, to avoid adding awkward arguments to controlset_url:

• theadd_url method is there so you can add an URL to a remote
• anddelete_url method is to delete one.

Finally, I've added a test covering all the new code, with a couple of edge cases, and wrote pydoc for those functions. I hope it's how you like it, mates!

I rolled back theurls property, because that was failing on Travis, which isn't using latest git.

Thegit remote get-url API has been introduced ingit 2.7.0, and wasn't availablebefore.

can you ping me when you think you'll be able to merge, and publish on pypi¸ and what version that will be? So I can update my setup.py accordingly ☺

If@nvie doesn't beat me to it, I will get the new release on the way on my next maintenance slot. Maybe tomorrow ... .

thank you ;-)

preparing my own code to be ready to point to the right version! :-)

I'll add 2 more bug fixes tonight to this release. After I'm done with those, I'll roll a new release :)