GitCentral 1.2.0

  • Improvements to Sync/GetLatest:
    • Added confirmation dialog for reloading assets after getting latest. It is recommended to always reload but you may skip it at your own risk.
    • GetLatest will no longer be considered failed when the repository is up to date
    • GetLatest will only reload the packages that were changed by the operation
    • GetLatest will no longer report errors when resolving conflicts with locally committed files
  • Newly added directories will no longer show up as deleted in the submit dialog. Instead, all of their untracked contents will show as added files to be submitted.
  • Checking in files will only attempt to unlock if their status was locked. This should have a significant impact on check-in performance especially with lots of files.
  • Moved status file from ./.gitcentral to ./.git/gitcentral/status. This makes it transparent and works like other git extensions.
  • Fixed an issue where the source control could be considered connected while git binary was not found

GitCentral 1.1.1

  • Locking is now enabled by default

GitCentral 1.1.0

  • Added support for manipulating Plugin Content assets
  • Fixed an issue where a successful operation would report failure, displaying the following error dialog: "Check-in failed as a result of save failure".

GitCentral 1.0.2

  • Added editor console commands to print internal state of GitCentral for debugging. Try gitcentral.XXX
  • Fixed an issue with whitespaces either in the Locks username configured or in the output of git lfs locks heaving trailing whitespaces. Now only the trimmed usernames are compared.

GitCentral 1.0.1

  • Added Verbose logging option for easier debugging and support

GitCentral 1.0.0

  • Git LFS Locking can be enabled in the source control connection dialog
  • Files will be locked by the current user when checking out or deleting, and unlocked when reverting or checking in
  • Files must be up to date before they can be checked out and locked
  • Files locked by others will appear as such and can no longer be checked out
  • Files can be forced writeable and edited locally while another user has the lock, the action is available in the contextual menu. Note that forced writeable files will not automatically acquire a lock once the other user has released the lock.
  • Files that are checked-out or modified locally but not locked can be locked through a new contextual action.
  • In order for locking to work properly, the git username and the remote repository username returned when calling 'git lfs locks' must match. This is entirely dependent on your lfs hosting provider, therefore you must adjust your username accordingly.
  • Force unlock is available in the contextual menu when enabling Administrator features in the source control dialog
  • Fixed an issue where the cached source control states may not have been properly updated under rare conditions
  • Fixed an issue that prevented a file from correctly being detected as added locally after being deleted remotely
  • Fixed an issue where the configuration file would not be written properly
  • Fixed an issue where changing source control configuration did not properly update the states