Git

### Features To make deploying your website even easier, Plesk Onyx introduces integration with Git - the most popular source code management system. An awesome upgrade from the older extension, Gitman, Git extension allows you to do the following: - Easily deploy your website content by either pushing it to a local Git repository or by pulling from a remote one. - Use GitHub, BitBucket, Travis, or any other software engineering service of your choice. - Create multiple branches in a single repository - useful for separating staging and production code. - Deploy manually for complete control or enable automatic deployment to save time. ### Licensing This extension is provided for **Free**. [Learn More](https://docs.plesk.com/en-US/onyx/administrator-guide/website-management/git-support.75824/)

# 1.1.2 (04 July 2019) * [-] Fixed the look of the Git section on the "Add Domain" screen. (EXTGIT-85) * [-] Pulling updates no longer fails with the "Call to a member function websiteOverviewUrl() on null" error. (EXTGIT-88) # 1.1.1 (27 December 2018) * [-] .local TLD can now be specified in the remote repository URL. (EXTGIT-75) * [-] Improved the "Adding Your Own Subscription" screen: selection of a service plan was moved from the Git extension section to the Subscription one.(EXTGIT-73) * [-] If Italian was set as the administrator's interface language, Git repositories can now be removed via the interface without any issues. (EXTGIT-65) * [-] If the `actions` node is empty, XML API calls to Git repositories are now executed without PHP notices and warnings. (EXTGIT-48) # 1.1.0 (13 April 2017) * [-] When checking out a repository, users could only select existing directories for the deploy path. (EXTGIT-34) * [-] Users could not create subdomains for addon domains with hosting type set to "Forwarding". (EXTGIT-38) * [-] Under specific circumstances, if more than one repository was checked out for a single domain, trying to remove a repository resulted in a different repository being removed instead. (EXTGIT-39) * [-] Git repositories could not be created if deployment mode was set to "No Deployment". (EXTGIT-40) * [-] After changing the deployment mode of an existing repository from "No Deployment" to "Automatic Deployment", an absolute deploy path was displayed instead of one relative to the subscription's root. (EXTGIT-41) * [-] Users could not authenticate with local Git repositories belonging to subdomains after the subscription's system user password was changed. (EXTGIT-45)