Release Notes

Fixes

Settings are now available when there's no repository yet
#4 Locking fails when the project is in a subfolder of the repository
#6 Serialization depth warning
#13 Remote is not recognized immediately after saving it
Fixed issue where user cannot lock files immediately after initializing repository, restart required
Fixed issue where pull operation still executes despite being notified there are local changes
Fixed issue where paths were not properly escaped when locking/unlocking files
Fixed issue where the status icon of a file in the asset window was not updated until the file lost focus
Fixed issue where the changes tree view did not show a status icon on the first file
Fixed issue where the project would appear uninitialized after closing and reopening the GitHub plugin window
Fixed issue where status icons did not appear in the project window and changes tree view when the project directory is a child of the repository root

#1 Missing x86 support
#5 Push action never ends and freezes Unity
#10 UTF-8 commit messages display incorrectly in history view
Make sure a git user and email address are set in the user .gitconfig
OS X users need latest git and git-lfs manually installed
Pushing to a new repository requires manually creating it on github.com and configuring it in the settings.
A single successful login is required. Authentication status is incorrectly reported.
Although an icon appears on locked files, there is no warning when attempting to modify a locked file.
Locks are not automatically released after a commit. Locks need to be manually released after use.