-title:Create Codefresh account

url:"/create-codefresh-account"

-title:CI/CD quick starts

url:"/ci-quickstart"

url:"/ci-quick-start"

sub-pages:

-title:Pipeline quick start

url:"/create-ci-pipeline"

-title:On-demand environment quick start

url:"/on-demand-environments"

-title:GitOps quick starts

url:"/gitops-quickstart"

url:"/gitops-quick-start"

sub-pages:

-title:Provision a hosted runtime

url:"/install-hosted"

toc:true

Codefresh integrates with the Git provider defined for your runtime account to sync repositories to your clusters, implementing Git-based operations when creating resources such as Delivery Pipelines, applications, and enriching images with valuable information.

Codefresh integrates with the Git provider defined for yourGitOpsruntime account to sync repositories to your clusters, implementing Git-based operations when creating resources such as Delivery Pipelines, applications, and enriching images with valuable information.

As the account administrator, you can select the authentication method for a runtime account. Users in Codefresh will then authorize access to the Git providers through the defined mechanism.

The[Authentication](https://g.codefresh.io/2.0/account-settings/authentication?providerName=github){:target="\_blank"} page displays the accounts by Git provider and the authentication method selected for the same.

The[GitAuthentication](https://g.codefresh.io/2.0/account-settings/authentication?providerName=github){:target="\_blank"} page displays the accounts by Git provider and the authentication method selected for the same.

Authentication accounts are organized by Runtimes. A runtime can have a single authentication account.

The Type column identifies the authentication for the provider account as either Codefresh, Custom, or PAT (personal access token).

max-width="80%"

%}

As the account administrator, you can change the authentication method foran accountat any time to either Codefresh or Custom, or manual token entry. See[Select authentication mechanism for runtime](#select-authentication-mechanism-for-runtime).

As the account administrator, you can change the authentication method fora Hybrid GitOps runtimeat any time to either Codefresh, Custom, or manual token entry. See[Select authentication mechanism for runtime](#select-authentication-mechanism-for-runtime).

Create a custom OAuth2 Application for Codefresh in your Git provider accounts with the correct scopes, and set up authentication for the same within Codefresh. Users in Codefresh can then authorize access to the Git provider using OAuth2, instead of a personal access token.

For a Git provider and a runtime account, select the authentication mechanism:Codefresh account, Custom provider account if one exists, or token-based authentication.

toc:true

Integrate Codefresh CI with Hosted GitOps for deployments powered by managed Argo CD.

Integrate Codefresh CIpipelineswith Hosted GitOps for deployments powered by managed Argo CD.

Codefresh Hosted GitOps includes a dedicated report image step that both reports and enriches deployed images. Add the report image step in your Codefresh CI pipeline and reference integrations with issue-tracking and container registry tools for Codefresh to retrieve and enrich image information.