Jun 20, 2023 · May 4, 2023 · May 8, 2023 · May 8, 2023 · May 8, 2023 · May 9, 2023
diff --git a/_docs/installation/gitops/hosted-runtime.md b/_docs/installation/gitops/hosted-runtime.md
  The Shared Configuration Repository is a centralized Git repository that stores configuration settings for the Hosted GitOps Runtime. Additional Hybrid runtimes provisioned for the account can point to this repo to retrieve and reuse the configuration.
  Read about [Shared Configuration Repositories]({{site.baseurl}}/docs/installation/gitops/shared-configuration/).


 * Git Source application repo
  Codefresh creates a Git Source application repo for every Hosted GitOps Runtime.
  Read about [Git sources]({{site.baseurl}}/docs/installation/gitops/git-sources/).
diff --git a/_docs/installation/gitops/monitor-manage-runtimes.md b/_docs/installation/gitops/monitor-manage-runtimes.md
 ## Configure SSH for GitOps Runtimes
 By default, Git repositories use the HTTPS protocol. You can also use SSH to connect Git repositories by entering the SSH private key.

 >When SSH is configured for a runtime, when creating/editing Git-Source applications, you can select HTTPS OR SSH as the protocol to connect to the Git repository. See [Repository URL in Application Source definitions]({{site.baseurl}}/docs/deployments/gitops/create-application/#source).
 >**NOTE**:
 When SSH is configured for a GitOps Runtime, when creating/editing Git-Source applications, you can select HTTPS OR SSH as the protocol to connect to the Git repository. See [Repository URL in Application Source definitions]({{site.baseurl}}/docs/deployments/gitops/create-application/#source).

 **SSH keys**
 For more information on generating SSH private keys, see the official documentation:
 * [GitHub](https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent){:target="\_blank"}
 * [GitLab](https://docs.gitlab.com/ee/ssh/#generating-a-new-ssh-key-pair){:target="\_blank"}
 * [Bitbucket](https://confluence.atlassian.com/bitbucket/set-up-an-ssh-key-728138079.html){:target="\_blank"}
 * [Azure](https://docs.microsoft.com/en-us/azure/devops/repos/git/use-ssh-keys-to-authenticate?view=azure-devops&tabs=current-page){:target="\_blank"}
 * [Gerrit](http://ec2-52-87-125-161.compute-1.amazonaws.com:8080/Documentation/user-upload.html#configure_ssh_public_keys){:target="\_blank"}

 **Before you begin**
 Copy the SSH private key for your Git provider
diff --git a/_docs/integrations/git-providers.md b/_docs/integrations/git-providers.md
 * GitLab On-premises
 * Azure DevOps Git
 * Atlassian Stash (old version of Bibucket Server)
 * Gerrit



 Atlassian Stash/Bitbucket server, as well as the on-premises version of GitLab and GitHub, are only available to Codefresh enterprise customers.
 *[GitLab documentation](https://docs.gitlab.com/ee/ssh/#generating-a-new-ssh-key-pair){:target="\_blank"}
 *[Bitbucket documentation](https://confluence.atlassian.com/bitbucket/set-up-an-ssh-key-728138079.html){:target="\_blank"}
 *[Azure documentation](https://docs.microsoft.com/en-us/azure/devops/repos/git/use-ssh-keys-to-authenticate?view=azure-devops&tabs=current-page){:target="\_blank"}
 *[Gerrit documentation](http://ec2-52-87-125-161.compute-1.amazonaws.com:8080/Documentation/user-upload.html#configure_ssh_public_keys){:target="\_blank"}

 ##GitHub

 1. Click the**Members** tab, and click**Add Members**.
 1. Type the email address of the Codefresh user, and select the user from the search results.
 1. Click**Add**.
 1. Browse to**Repositories** and select the repository for which to set permissions.
 1. Browse to**Repositories** and select the repository for which to set permissions, and do the following:
 1. Select**Access > Edit**, and set the following permissions:
 ***Reference**: Set to**refs/***
 ***Read**:**ALLOW** for Service Users
 ***Owner**:**ALLOW** for Service Users as`webhooks.config` in`refs/meta/config` requires[owner-level permissions](https://gerrit-review.googlesource.com/Documentation/access-control.html#category_submit){:target="\_blank"}.
 ***Label Verified**:**-1**,**+1** for Service Users. Gives permission to apply the`Verified` label with either a`-1` or`+1` value.
 ***Read**:**ALLOW** for Service Users to read branches.
          Note that you can also set this permission at the level of**All projects**.

 ***Owner**:**ALLOW** for Service Users to create webhooks for pipeline triggers.
 `webhooks.config` in`refs/meta/config` requires[owner-level permissions](https://gerrit-review.googlesource.com/Documentation/access-control.html#category_submit){:target="\_blank"}.
          Note that this permission must be set only at the_repository-level_.

 ***Label Verified**:**-1**,**+1** for Service Users.
          Gives permission to apply the`Verified` label, which is the typical label for CI, with either a`-1` or`+1` value.
          Note that you can also set this permission at the level of**All projects**.

 1. Continue with[Step 2: Generate password for user in Gerrit](#step-2-generate-password-for-user-in-gerrit).

 ###Step 2: Generate password for user in Gerrit
diff --git a/_docs/pipelines/variables.md b/_docs/pipelines/variables.md

 ## Gerrit changeId & change message variables


 Gerrit has no explicit concept of pull requests, as in other version control systems, to map trigger event payloads to builds. Instead, Gerrit uses `Changes` which serves a similar purpose and functionality as pull requests. You can achieve the same functionality in Codefresh with our `CF_PULL_REQUEST` group of environment variables.


 {: .table .table-bordered .table-hover}
 | Variable        | Description                                            |
 | --------------- | ------------------------------------------------------ |
Original file line number	Diff line number	Diff line change
Expand Up		@@ -158,6 +158,7 @@ Once you authorize access, Codefresh creates two Git repositories, one to store
		The Shared Configuration Repository is a centralized Git repository that stores configuration settings for the Hosted GitOps Runtime. Additional Hybrid runtimes provisioned for the account can point to this repo to retrieve and reuse the configuration.
		Read about [Shared Configuration Repositories]({{site.baseurl}}/docs/installation/gitops/shared-configuration/).


		* Git Source application repo
		Codefresh creates a Git Source application repo for every Hosted GitOps Runtime.
		Read about [Git sources]({{site.baseurl}}/docs/installation/gitops/git-sources/).
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -111,14 +111,16 @@ Here is a description of the information in the Topology view.
		## Configure SSH for GitOps Runtimes
		By default, Git repositories use the HTTPS protocol. You can also use SSH to connect Git repositories by entering the SSH private key.

		>When SSH is configured for a runtime, when creating/editing Git-Source applications, you can select HTTPS OR SSH as the protocol to connect to the Git repository. See [Repository URL in Application Source definitions]({{site.baseurl}}/docs/deployments/gitops/create-application/#source).
		>NOTE:
		When SSH is configured for a GitOps Runtime, when creating/editing Git-Source applications, you can select HTTPS OR SSH as the protocol to connect to the Git repository. See [Repository URL in Application Source definitions]({{site.baseurl}}/docs/deployments/gitops/create-application/#source).

		SSH keys
		For more information on generating SSH private keys, see the official documentation:
		* [GitHub](https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent){:target="\_blank"}
		* [GitLab](https://docs.gitlab.com/ee/ssh/#generating-a-new-ssh-key-pair){:target="\_blank"}
		* [Bitbucket](https://confluence.atlassian.com/bitbucket/set-up-an-ssh-key-728138079.html){:target="\_blank"}
		* [Azure](https://docs.microsoft.com/en-us/azure/devops/repos/git/use-ssh-keys-to-authenticate?view=azure-devops&tabs=current-page){:target="\_blank"}
		* [Gerrit](http://ec2-52-87-125-161.compute-1.amazonaws.com:8080/Documentation/user-upload.html#configure_ssh_public_keys){:target="\_blank"}

		Before you begin
		Copy the SSH private key for your Git provider
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -26,6 +26,8 @@ Currently Codefresh supports:
		* GitLab On-premises
		* Azure DevOps Git
		* Atlassian Stash (old version of Bibucket Server)
		* Gerrit



		Atlassian Stash/Bitbucket server, as well as the on-premises version of GitLab and GitHub, are only available to Codefresh enterprise customers.
Expand DownExpand Up		@@ -88,6 +90,7 @@ For more information on generating SSH keys and adding your public key to your V
		*[GitLab documentation](https://docs.gitlab.com/ee/ssh/#generating-a-new-ssh-key-pair){:target="\_blank"}
		*[Bitbucket documentation](https://confluence.atlassian.com/bitbucket/set-up-an-ssh-key-728138079.html){:target="\_blank"}
		*[Azure documentation](https://docs.microsoft.com/en-us/azure/devops/repos/git/use-ssh-keys-to-authenticate?view=azure-devops&tabs=current-page){:target="\_blank"}
		*[Gerrit documentation](http://ec2-52-87-125-161.compute-1.amazonaws.com:8080/Documentation/user-upload.html#configure_ssh_public_keys){:target="\_blank"}

		##GitHub

Expand DownExpand Up		@@ -360,12 +363,20 @@ Gerrit has a special Service Users access-group for CI systems and other bot
		1. Click theMembers tab, and clickAdd Members.
		1. Type the email address of the Codefresh user, and select the user from the search results.
		1. ClickAdd.
		1. Browse toRepositories and select the repository for which to set permissions.
		1. Browse toRepositories and select the repository for which to set permissions, and do the following:
		1. SelectAccess > Edit, and set the following permissions:
		*Reference: Set torefs/*
		*Read:ALLOW for Service Users
		*Owner:ALLOW for Service Users as`webhooks.config` in`refs/meta/config` requires[owner-level permissions](https://gerrit-review.googlesource.com/Documentation/access-control.html#category_submit){:target="\_blank"}.
		*Label Verified:-1,+1 for Service Users. Gives permission to apply the`Verified` label with either a`-1` or`+1` value.
		*Read:ALLOW for Service Users to read branches.
		Note that you can also set this permission at the level ofAll projects.

		*Owner:ALLOW for Service Users to create webhooks for pipeline triggers.
		`webhooks.config` in`refs/meta/config` requires[owner-level permissions](https://gerrit-review.googlesource.com/Documentation/access-control.html#category_submit){:target="\_blank"}.
		Note that this permission must be set only at the_repository-level_.

		*Label Verified:-1,+1 for Service Users.
		Gives permission to apply the`Verified` label, which is the typical label for CI, with either a`-1` or`+1` value.
		Note that you can also set this permission at the level ofAll projects.

		1. Continue with[Step 2: Generate password for user in Gerrit](#step-2-generate-password-for-user-in-gerrit).

		###Step 2: Generate password for user in Gerrit
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -207,8 +207,10 @@ When a pull request is closed in GitHub, the following variables are also availa

		## Gerrit changeId & change message variables


		Gerrit has no explicit concept of pull requests, as in other version control systems, to map trigger event payloads to builds. Instead, Gerrit uses `Changes` which serves a similar purpose and functionality as pull requests. You can achieve the same functionality in Codefresh with our `CF_PULL_REQUEST` group of environment variables.


		{: .table .table-bordered .table-hover}
		\| Variable \| Description \|
		\| --------------- \| ------------------------------------------------------ \|
Expand Down