Release Notes

Enhancements & Fixes

• The extension now remembers your "Trace Logging" preference between Unity restarts
• The extension now remembers your login between Unity restarts
• Fixed possible error that can occur when first attempting to create a branch
• Locking/unlocking files no longer fails with missing credentials error on Windows
• Fixed scenario where authentication window hangs on error
• Fixed a handful of exceptions when entering play mode
• #16 Fix error that can occur displaying the authentication window

Known Issues

• #5 Push action never ends and freezes Unity
• #32 Missing Unity 5.3 support
• 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.
• 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.

Release Notes

Enhancements & Fixes

• #1 Added x86 support
• #8 Native file watcher now loads correctly on Windows 10
• #10 Improve Unicode support in the History tab
• #17 HistoryView no longer throws NRE on initialize
• #22 Fix NREs that could crash Unity
• #31 #11 Project Window icon overlay improvements
• GitHub window no longer takes focus on startup/enable
• Fixed git execution environment that was keeping rebase and merge from working correctly
• Configure the Unity YAML Merge tool when initializing a repo

Known Issues

• Previous versions must be deleted before starting Unity
• #5 Push action never ends and freezes Unity
• #32 Missing Unity 5.3 support
• Make sure a git user and email address are set in the user .gitconfig before initializing a repository
• 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.

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

Known Issues

• #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.

Release Notes, 0.8-alpha

Features

• Initialize repository
• Commit
• Push
• Pull
• Create and switch branches
• Lock/unlock files

Known Issues

• Limited OS X support - changes to files inside Unity will be tracked, but the UI won't fully update after commits, pulls or other git actions.
• The authentication window doesn't correctly track whether the user has already logged in or not, but the credentials will be used correctly, so you only need to login once.
• If a file has been locked by someone else, an icon will appear in the project window. However, there is no warning when attempting to modify such a locked file.
• Locks are not automatically released after commits have been pushed. You should release locks after you've pushed you work.
• When entering play mode, the UI flickers and/or disappears briefly.