Feature Pretty names for github SVN

[Theraze]

> svn checkout https://github.com/Ezandora/Guide/branches/Release/

Starting Checkout...
Validating repo...
Repo validated.
C:\Program Files (x86)\KoLmafia\svn\630e5f8f-ebb2-ad18-345f-ce57b7db7bff
A https://github.com/Ezandora/Guide/branches/Release/relay
A https://github.com/Ezandora/Guide/branches/Release/relay/relay_Guide.ash
A https://github.com/Ezandora/Guide/branches/Release/relay/relay_Guide.js
https://github.com/Ezandora/Guide/branches/Release
At revision 40

Successfully checked out working copy.
Pushing local updates...
relay_Guide.js => C:\Program Files (x86)\KoLmafia\relay\relay_Guide.js
relay_Guide.ash => C:\Program Files (x86)\KoLmafia\relay\relay_Guide.ash
Done.
Requests complete.

If there is any way that we could get a more descriptive name than 630e5f8f-ebb2-ad18-345f-ce57b7db7bff for scripts like this, that would be nice...

This being the script from http://kolmafia.us/showthread.php?14784-Guide.

 

[Crowther]

630e5f8f-ebb2-ad18-345f-ce57b7db7bff might not be descriptive, but it sure is unique!

 

[lostcalpolydude]

It would help to have more than 1 example to have a good idea of which part of the URL would make sense. Currently it looks like the username would have to be part of the name, which is different from sourceforge and googlecode but obviously an improvement over the hash that we currently use.

 

[roippi]

r13539

Not sure if it will break anything for currently-installed users.

If there's a more succinct way of unique-izing the URL, we can do that. I just used everything after github.com.

 

[xKiv]

630e5f8f-ebb2-ad18-345f-ce57b7db7bff might not be descriptive, but it sure is unique!

Nitpick: it's *highly likely* to be unique (with some assumptions on the space of possible non-hashed values).
I mean, it's only 16 bytes. So it *can't* be guaranteed unique for anything with more than 16 bytes of data, for one.