v1.7.12

v1.7.12 fixes clone, fetch and push from the siGit desktop app.

#Git responses no longer carry a charset

sigit.si sent its git responses with ; charset=utf-8 after the media type, for example application/x-git-upload-pack-advertisement; charset=utf-8. The git command line accepts that. The library the desktop app uses compares the header exactly, so it refused the response with "invalid content-type", and clone, fetch and push from the app all failed.

The git media types now go out without the charset on the ref advertisements and on the upload-pack and receive-pack results. Nothing changes for the git command line.

#Publishing from the app could leave an empty repository behind

Publishing creates the repository first and then pushes. When the push failed for the reason above, the empty repository stayed on your account, and publishing again was refused because the name was taken. With pushes working this stops happening. Any empty repository an earlier attempt left behind can be deleted from its settings page.