Feb 17, 2025 · Feb 12, 2025 · Feb 12, 2025 · Feb 12, 2025 · Feb 12, 2025 · Feb 13, 2025
diff --git a/_docs/installation/gitops/git-sources.md b/_docs/installation/gitops/git-sources.md
 The Git Source connects to a Git repository within your organization, serving as an easy way to manage the deployment and configuration of Argo CD applications on clusters.
 The Git repository referenced by the Git Source stores application manifests and other resources which are always synced to the cluster. Codefresh manages the Git Source itself as an Argo CD application.

 <br>
 Watch this video:
 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Git Sources in Runtimes](https://www.youtube.com/watch?v=StKxdCcOIQc&t=2s){:target="\_blank"}

 ##### Types of Git Sources
 Codefresh allows you to create two types of Git Sources: Standard and Restricted Git Sources.
diff --git a/_docs/installation/gitops/runtime-concepts.md b/_docs/installation/gitops/runtime-concepts.md
 During installation, you need to provide the URL to the Git repository defined as the Shared Configuration Repo, using only the repository URL, or by adding the path, reference a branch, or both.
 Codefresh identifies the Git provider from the URL provided, and for cloud providers, automatically populates the Git Provider and the API URL fields.

 For information on the structure and settings, see [Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/).
 Watch this video for an overview:
 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Shared Configuration Repository](https://www.youtube.com/watch?v=7WNoNZ58IzU){:target="\_blank"}

 For detailed information, see [Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/).



 ## Configuration Runtimes
 A Configuration Runtime is a GitOps Runtime designated to manage platform-level resources that are not tied to a specific Runtime. These resources, essential for features like products and promotions in GitOps ensure smooth platform operations.

 You can add a Git Source as part of the Runtime installation, or after installation whenever required. The same Runtime can have multiple Git Sources. Codefresh manages the Git Source itself as an Argo CD application.

 For information on the different types of Git Sources, their settings and usage, see [Managing Git Sources in GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/git-sources/).
 Watch this video for an overview:
 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Git Sources in Runtimes](https://www.youtube.com/watch?v=StKxdCcOIQc&t=2s){:target="\_blank"}

 For detailed information, see [Managing Git Sources in GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/git-sources/).

 ## External clusters in Runtimes
 GitOps Runtimes allow you to extend your application deployments to external clusters, enabling centralized management without requiring Argo CD installations on each cluster.
diff --git a/_docs/installation/gitops/shared-configuration.md b/_docs/installation/gitops/shared-configuration.md
 ## Shared Configuration Repository
 A Codefresh account with <!--- a Hosted or -->a Hybrid GitOps Runtime can store configuration manifests for account-level resources in a Git repository. This repository, the Shared Configuration Repository, can be shared with other GitOps Runtimes in the same account, avoiding the need to create and maintain different configuration manifests for every GitOps Runtime. At the same time, you also have the flexibility to store resources unique to specific Runtimes without affecting other Runtimes.

 Watch this video for an overview:
 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Shared Configuration Repository](https://www.youtube.com/watch?v=7WNoNZ58IzU){:target="\_blank"}


 ##### When is it created?
 The Shared Configuration Repository (internally ISO/iso) is created on installing the first Hybrid GitOps Runtime in the account. See [GitOps Runtimes & Shared Configuration Repos](#gitops-runtimes--shared-configuration-repos).


 {{site.data.callout.callout_warning}}
 **IMPORTANT**
 Only _Codefresh account administrators should have access_ to the Shared Configuration Repository. Its content is automatically generated and maintained by Codefresh.
  Currently, Codefresh supports a single Shared Configuration Repo per account.
  You may need to reset the Shared Configuration Repo after creating it. See [Reset Shared Configuration Repository for GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#reset-shared-configuration-repository-for-gitops-runtimes).  -->

 ### Shared Configuration Repo URL formats
 ## Shared Configuration Repo URL formats
 When defining the Shared Configuration Repository for the account, you have the option to specify a path, a branch, or both, within the repository URL.
 This allows for flexibility in targeting specific directories or branches in the repository.

diff --git a/_docs/products/about-products.md b/_docs/products/about-products.md
 ## Products in Codefresh GitOps
 Harness the power of **Products** in Codefresh GitOps to streamline the management and deployment of Argo CD applications.

 A Product groups related Argo CD applications, providing a unified perspective as the applications progress through different stages of development and deployment. By defining relationships between applications across multiple environments, Products introduce an organizational layer providing context that help manage application releases as a cohesive unit.\
 A Product groups related Argo CD applications, providing a unified perspective as the applications progress through different stages of development and deployment. By defining relationships between applications across multiple environments, Products introduce an organizational layer providing context that help manage application releases as a cohesive unit.

 Watch this video:
 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Explore Products](https://www.youtube.com/watch?v=m3wE4OfV9xE){:target="\_blank"}

 {% include
 image.html
 max-width="70%"
 %}

 ## Boosting application management with Products


 ##### Boosting application management with Products
 Products enhance and simplify application management by enabling controlled promotions, version tracking, and environment-specific configurations.
 Since an application can exist in multiple environments, grouping them within a Product helps compare versions, track changes, and maintain consistency.

 Read more about the dashboard in this [blog](https://codefresh.io/blog/introducing-the-worlds-first-dashboard-for-gitops-environments/){:target="\_blank"}.


 ### Key benefits
 ##### Key benefits
 * **Unified application management**
  Grouping interconnected applications simplifies management and streamlines deployments across environments.

 After [creating products]({{site.baseurl}}/docs/products/create-product/), assign applications, streamline their promotions, and gain visibility across environments.
 See [Assigning applications to the product]({{site.baseurl}}/docs/products/assign-applications/).

 ## Promotions and promotion settings for Products
 ## Promotion settings and promotions for Products

 Promotion settings for a product define what changes can be advanced and under what conditions, ensuring that each promotion aligns with your deployment strategy.
 These settings provide control over:
 * **Version source for applications**: Specify where application versions originate to maintain consistency across environments.
 * **Promotable properties in applications**: Define precisely which settings are carried forward during a promotion.
 * **Promotion Flows**: Assign the Promotion Flows most relevant to the Product, and configure the conditions that trigger each flow.
 See [Application version and promotable properties]({{site.baseurl}}/docs/products/promotion-version-properties/) and [Promotion flows and triggers for products]({{site.baseurl}}/docs/products/promotion-flow-triggers/).

 Promote a product manually to a specific environment or automate promotions across multiple environments using Promotion Flows.
 See [Triggering promotions]({{site.baseurl}}/docs/promotions/trigger-promotions/).

 **Promotion settings for Products** give you control over what and how changes are advanced, ensuring that each promotion aligns with your deployment strategy.

 Customize promotion settings to configure:
 * **Version source for applications**: Maintain consistency by specifying where application versions originate.
 * **Promotable attributes in applications**: Define which changes are promoted across different environments.
 * **Promotion Flows**: Select the Promotion Flows that match the Product, and tailor the conditions to trigger each of these flows.

 See [Application version and promotable properties]({{site.baseurl}}/docs/products/promotion-version-properties/) and [Promotion flows and triggers for products]({{site.baseurl}}/docs/products/promotion-flow-triggers/).


 {% include
 image.html
 lightbox="true"
 max-width="60%"
 %}


 Watch this video:
 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Dive into Promotion Settings for Products](https://www.youtube.com/watch?v=AjFhoja8TjY){:target="\_blank"}

 ## Tracing Product promotions through Releases
 Whenever a Product is promoted, Codefresh GitOps generates a Release, capturing the promotion orchestration across environments. The Releases tab of the product lists both ongoing and completed releases, from where you can monitor specific releases.
diff --git a/_docs/products/configure-product-settings.md b/_docs/products/configure-product-settings.md
 * [Promotion Settings](#configure-promotion-settings-for-products)
  Define the version and properties to promote for the applications in the product either from a predefined promotion template, or by defining the promotion settings.


 Watch this video:
 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Dive into Promotion Settings for Products](https://www.youtube.com/watch?v=AjFhoja8TjY){:target="\_blank"}

 ## Form & YAML modes
 As with most GitOps entities, you have the option to configure Product Settings in Form or YAML modes, and switch seamlessly between them during configuration.
diff --git a/_docs/promotions/promotion-flow.md b/_docs/promotions/promotion-flow.md
 - /docs/promotions/entities/
 toc: true
 ---
 ## Promotion Flows in Codefresh GitOps
 A Promotion Flow is a sequence of automated actions that systematically move code changes through environments, from development to production. This structured approach enhances deployment reliability and efficiency, ensuring changes meet quality standards before reaching end users.

 Promotion Flows allow teams to manage their software delivery pipelines with precision, defining conditions, dependencies, and actions for each environment. Whether deploying to staging, production, or custom environments, Promotion Flows provide flexibility and control over your continuous delivery process.
 Backed by the power of Argo CD, streamline the process of moving code changes through different stages, minus all the manual work of custom scripting to manage environment-specific requirements.

 Watch this video:
 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Promotion Flows](https://www.youtube.com/watch?v=M8G-AY7FIIg){:target="\_blank"}

 {% include
 image.html
 lightbox="true"
diff --git a/_docs/promotions/promotions-overview.md b/_docs/promotions/promotions-overview.md
 toc: true
 ---

 ## Promotions in Codefresh GitOps
 Continuous Delivery (CD) is an essential practice in the Software Development Lifecycle (SDLC) that automates the release process, ensuring consistent and reliable deployment of application updates across environments. CD bridges the gap between development and operations, empowering teams to deliver changes to production with speed and confidence.

 A core element of CD is **promotion** - the process of advancing an application version through environments, such as from staging to production, based on predefined criteria or approvals. Promotion sequences ensure that only validated, stable versions of applications only validated, stable versions reach production, reducing risk with every release.

 ## Getting started with promotions in GitOps

 Review these articles to begin with promotions in Codefresh GitOps:
 ##### Walk through with quick starts
 Dive into [quick starts on promotions]({{site.baseurl}}/docs/gitops-quick-start/promotions/)<!--- ({{site.baseurl}}/docs/gitops-quick-start/)--> for step-by-step guides to get started efficiently.

 ### Promotions with GitOps: The Codefresh advantage
 Watch this video to see a promotion in action:
 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Drag-and-drop Promotion](https://www.youtube.com/watch?v=4isYoutmRco&t=1s){:target="\_blank"}


 ##### Understand the components and entities
 Explore [Promotion building blocks]({{site.baseurl}}/docs/promotions/promotion-components/) to learn about the key entities and how they fit together in the promotion process.

 ##### Set up and configure promotions
 Follow the guidelines in [Promotions: Setup & configuration]({{site.baseurl}}/docs/promotions/create-promotion-sequence/) to configure, trigger, and monitor promotions.

 Watch this video to learn how to configure an automated Promotion Flow:
 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Promotion Flows](https://www.youtube.com/watch?v=M8G-AY7FIIg&t=76s){:target="\_blank"}

 ## Promotions with GitOps: The Codefresh advantage
 Codefresh builds on the power of GitOps by fully integrating promotions into its framework, giving you enhanced visibility, control, and automation, with Git as the single source of truth.

 {% include
 >**NOTE**
 You need Runtime version 0.13.4 or higher to support GitOps promotions. Ensure your runtime is updated to at least this version to access  promotion features.

 ### GitOps promotion entities
 ## GitOps promotion entities
 Codefresh  GitOps provides specialized functionality to streamline and automate the promotion process, ensuring consistency and control without the need for custom scripts. These features allow you to design predictable reusable delivery lifecycles across products and environments, with all the required validations, reducing operational overhead and manual errors.

 * **Predefine properties to promote**
 <!--- screenshot of yaml examples to differentiate and not overcrowd -->


 ### Getting started with promotions in GitOps

 Review these articles to begin with GitOps promotions:
 * **Walk through with quick starts**: Dive into [quick starts on promotions]({{site.baseurl}}/docs/gitops-quick-start/promotions/)<!--- ({{site.baseurl}}/docs/gitops-quick-start/)--> for step-by-step guides to get started efficiently.
 * **Understand the components and entities**: Explore [Promotion building blocks]({{site.baseurl}}/docs/promotions/promotion-components/) to learn about the key entities and how they fit together in the promotion process.
 * **Set up and configure promotions**: Follow the guidelines in [Promotions: Setup & configuration]({{site.baseurl}}/docs/promotions/create-promotion-sequence/) to configure, trigger, and monitor promotions.



diff --git a/_docs/promotions/trigger-promotions.md b/_docs/promotions/trigger-promotions.md

 Promotions are a key component of the continuous delivery (CD) process, enabling teams to control how software moves through various environments based on automated triggers or manual inputs.

 Codefresh GitOps supports automated promotion sceanrios tailored to various deployment models through Promotion Flows, triggered on predefined criteria, such as specific commit messages or changes in Git branches, allowing seamless and consistent updates across environments. See [Creating Promotion Flows](#{{site.baseurl}}/docs/promotions/promotion-flow/).
 Codefresh GitOps supports automated promotion scenarios tailored to various deployment models through Promotion Flows, triggered on predefined criteria, such as specific commit messages or changes in Git branches, allowing seamless and consistent updates across environments.

 Watch the video:
 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Promotion Flows](https://www.youtube.com/watch?v=M8G-AY7FIIg){:target="\_blank"}

 See also [Creating Promotion Flows](#{{site.baseurl}}/docs/promotions/promotion-flow/).

 Recognizing that some scenarios require on-demand control, Codefresh also provides manual promotion triggers to handle specific needs. Whether deploying a hotfix to production, promoting an entire product release, or testing code changes in a targeted environment, manual promotion options offer flexibility to meet these demands.

 Watch the video:
 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/}[Drag-and-drop Promotion](https://www.youtube.com/watch?v=4isYoutmRco&t=1s){:target="\_blank"}

 Manual promotion triggers provide different levels of control, accessible from distinct areas of the platform, enabling:

 * **Single-environment promotion**
 Drag-and-drop the product to the target environment to promote changes, and customize the Promotion Settings to control promotion behavior for the environment.
 This method is useful to test changes within a specific environment. For example, QA teams wanting to test changes in staging or other internal environments.

 {::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Drag-and-drop promotions](https://www.youtube.com/watch?v=4isYoutmRco){:target="\_blank"}


 ##### Before you begin
diff --git a/assets/css/docs.min.css b/assets/css/docs.min.css
diff --git a/assets/css/docs.min.css.map b/assets/css/docs.min.css.map
diff --git a/assets/scss/_links.scss b/assets/scss/_links.scss
    &:not([href^="https://g.codefresh.io/"]):not([href*="/docs/"]):not([href^="#"]){
      @include external-link("external-link");
    }

    &[href^="https://www.youtube.com/"] {
      &::after {
        display: none !important;
      }
    }
  }
 }
diff --git a/images/icons/video-play-blue-small-5x.png b/images/icons/video-play-blue-small-5x.png
diff --git a/images/icons/video-play-blue-small.png b/images/icons/video-play-blue-small.png
diff --git a/images/icons/video-play-icon-blue.png b/images/icons/video-play-icon-blue.png
diff --git a/images/icons/video-play-icon-blue.svg b/images/icons/video-play-icon-blue.svg
diff --git a/images/icons/video-play-icon.png b/images/icons/video-play-icon.png
Original file line number	Diff line number	Diff line change
Expand Up		@@ -10,7 +10,8 @@ A Git Source is a unique entity created for use with GitOps Runtimes in Codefres
		The Git Source connects to a Git repository within your organization, serving as an easy way to manage the deployment and configuration of Argo CD applications on clusters.
		The Git repository referenced by the Git Source stores application manifests and other resources which are always synced to the cluster. Codefresh manages the Git Source itself as an Argo CD application.

		<br>
		Watch this video:
		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Git Sources in Runtimes](https://www.youtube.com/watch?v=StKxdCcOIQc&t=2s){:target="\_blank"}

		##### Types of Git Sources
		Codefresh allows you to create two types of Git Sources: Standard and Restricted Git Sources.
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -46,7 +46,12 @@ The Shared Configuration Repository (internally `ISO`/`iso`), is created on inst
		During installation, you need to provide the URL to the Git repository defined as the Shared Configuration Repo, using only the repository URL, or by adding the path, reference a branch, or both.
		Codefresh identifies the Git provider from the URL provided, and for cloud providers, automatically populates the Git Provider and the API URL fields.

		For information on the structure and settings, see [Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/).
		Watch this video for an overview:
		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Shared Configuration Repository](https://www.youtube.com/watch?v=7WNoNZ58IzU){:target="\_blank"}

		For detailed information, see [Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/).



		## Configuration Runtimes
		A Configuration Runtime is a GitOps Runtime designated to manage platform-level resources that are not tied to a specific Runtime. These resources, essential for features like products and promotions in GitOps ensure smooth platform operations.
Expand All		@@ -62,7 +67,10 @@ The Git Source connects to a Git repository within your organization, and stores

		You can add a Git Source as part of the Runtime installation, or after installation whenever required. The same Runtime can have multiple Git Sources. Codefresh manages the Git Source itself as an Argo CD application.

		For information on the different types of Git Sources, their settings and usage, see [Managing Git Sources in GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/git-sources/).
		Watch this video for an overview:
		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Git Sources in Runtimes](https://www.youtube.com/watch?v=StKxdCcOIQc&t=2s){:target="\_blank"}

		For detailed information, see [Managing Git Sources in GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/git-sources/).

		## External clusters in Runtimes
		GitOps Runtimes allow you to extend your application deployments to external clusters, enabling centralized management without requiring Argo CD installations on each cluster.
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -7,9 +7,14 @@ toc: true
		## Shared Configuration Repository
		A Codefresh account with <!--- a Hosted or -->a Hybrid GitOps Runtime can store configuration manifests for account-level resources in a Git repository. This repository, the Shared Configuration Repository, can be shared with other GitOps Runtimes in the same account, avoiding the need to create and maintain different configuration manifests for every GitOps Runtime. At the same time, you also have the flexibility to store resources unique to specific Runtimes without affecting other Runtimes.

		Watch this video for an overview:
		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Shared Configuration Repository](https://www.youtube.com/watch?v=7WNoNZ58IzU){:target="\_blank"}


		##### When is it created?
		The Shared Configuration Repository (internally ISO/iso) is created on installing the first Hybrid GitOps Runtime in the account. See [GitOps Runtimes & Shared Configuration Repos](#gitops-runtimes--shared-configuration-repos).


		{{site.data.callout.callout_warning}}
		IMPORTANT
		Only _Codefresh account administrators should have access_ to the Shared Configuration Repository. Its content is automatically generated and maintained by Codefresh.
Expand DownExpand Up		@@ -61,7 +66,7 @@ See [Shared Configuration Repo structure](#shared-configuration-repo-structure).
		Currently, Codefresh supports a single Shared Configuration Repo per account.
		You may need to reset the Shared Configuration Repo after creating it. See [Reset Shared Configuration Repository for GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#reset-shared-configuration-repository-for-gitops-runtimes). -->

		### Shared Configuration Repo URL formats
		## Shared Configuration Repo URL formats
		When defining the Shared Configuration Repository for the account, you have the option to specify a path, a branch, or both, within the repository URL.
		This allows for flexibility in targeting specific directories or branches in the repository.

Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -11,7 +11,10 @@ toc: true
		## Products in Codefresh GitOps
		Harness the power of Products in Codefresh GitOps to streamline the management and deployment of Argo CD applications.

		A Product groups related Argo CD applications, providing a unified perspective as the applications progress through different stages of development and deployment. By defining relationships between applications across multiple environments, Products introduce an organizational layer providing context that help manage application releases as a cohesive unit.\
		A Product groups related Argo CD applications, providing a unified perspective as the applications progress through different stages of development and deployment. By defining relationships between applications across multiple environments, Products introduce an organizational layer providing context that help manage application releases as a cohesive unit.

		Watch this video:
		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Explore Products](https://www.youtube.com/watch?v=m3wE4OfV9xE){:target="\_blank"}

		{% include
		image.html
Expand All		@@ -23,7 +26,9 @@ caption="Products and Product Dashboard in GitOps"
		max-width="70%"
		%}

		## Boosting application management with Products


		##### Boosting application management with Products
		Products enhance and simplify application management by enabling controlled promotions, version tracking, and environment-specific configurations.
		Since an application can exist in multiple environments, grouping them within a Product helps compare versions, track changes, and maintain consistency.

Expand All		@@ -42,7 +47,7 @@ Explore the [Product Dashboard]({{site.baseurl}}/docs/dashboards/gitops-products
		Read more about the dashboard in this [blog](https://codefresh.io/blog/introducing-the-worlds-first-dashboard-for-gitops-environments/){:target="\_blank"}.


		### Key benefits
		##### Key benefits
		* Unified application management
		Grouping interconnected applications simplifies management and streamlines deployments across environments.

Expand All		@@ -69,21 +74,19 @@ There are two ways to create a Product in Codefresh GitOps:
		After [creating products]({{site.baseurl}}/docs/products/create-product/), assign applications, streamline their promotions, and gain visibility across environments.
		See [Assigning applications to the product]({{site.baseurl}}/docs/products/assign-applications/).

		## Promotions and promotion settings for Products
		## Promotion settings and promotions for Products

		Promotion settings for a product define what changes can be advanced and under what conditions, ensuring that each promotion aligns with your deployment strategy.
		These settings provide control over:
		* Version source for applications: Specify where application versions originate to maintain consistency across environments.
		* Promotable properties in applications: Define precisely which settings are carried forward during a promotion.
		* Promotion Flows: Assign the Promotion Flows most relevant to the Product, and configure the conditions that trigger each flow.
		See [Application version and promotable properties]({{site.baseurl}}/docs/products/promotion-version-properties/) and [Promotion flows and triggers for products]({{site.baseurl}}/docs/products/promotion-flow-triggers/).

		Promote a product manually to a specific environment or automate promotions across multiple environments using Promotion Flows.
		See [Triggering promotions]({{site.baseurl}}/docs/promotions/trigger-promotions/).

		Promotion settings for Products give you control over what and how changes are advanced, ensuring that each promotion aligns with your deployment strategy.

		Customize promotion settings to configure:
		* Version source for applications: Maintain consistency by specifying where application versions originate.
		* Promotable attributes in applications: Define which changes are promoted across different environments.
		* Promotion Flows: Select the Promotion Flows that match the Product, and tailor the conditions to trigger each of these flows.

		See [Application version and promotable properties]({{site.baseurl}}/docs/products/promotion-version-properties/) and [Promotion flows and triggers for products]({{site.baseurl}}/docs/products/promotion-flow-triggers/).


		{% include
		image.html
		lightbox="true"
Expand All		@@ -94,7 +97,8 @@ caption="Promotion settings for products"
		max-width="60%"
		%}


		Watch this video:
		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Dive into Promotion Settings for Products](https://www.youtube.com/watch?v=AjFhoja8TjY){:target="\_blank"}

		## Tracing Product promotions through Releases
		Whenever a Product is promoted, Codefresh GitOps generates a Release, capturing the promotion orchestration across environments. The Releases tab of the product lists both ongoing and completed releases, from where you can monitor specific releases.
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -26,7 +26,8 @@ This article describes how to configure the different Product Settings:
		* [Promotion Settings](#configure-promotion-settings-for-products)
		Define the version and properties to promote for the applications in the product either from a predefined promotion template, or by defining the promotion settings.


		Watch this video:
		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Dive into Promotion Settings for Products](https://www.youtube.com/watch?v=AjFhoja8TjY){:target="\_blank"}

		## Form & YAML modes
		As with most GitOps entities, you have the option to configure Product Settings in Form or YAML modes, and switch seamlessly between them during configuration.
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -7,11 +7,15 @@ redirect-from:
		- /docs/promotions/entities/
		toc: true
		---
		## Promotion Flows in Codefresh GitOps
		A Promotion Flow is a sequence of automated actions that systematically move code changes through environments, from development to production. This structured approach enhances deployment reliability and efficiency, ensuring changes meet quality standards before reaching end users.

		Promotion Flows allow teams to manage their software delivery pipelines with precision, defining conditions, dependencies, and actions for each environment. Whether deploying to staging, production, or custom environments, Promotion Flows provide flexibility and control over your continuous delivery process.
		Backed by the power of Argo CD, streamline the process of moving code changes through different stages, minus all the manual work of custom scripting to manage environment-specific requirements.

		Watch this video:
		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Promotion Flows](https://www.youtube.com/watch?v=M8G-AY7FIIg){:target="\_blank"}

		{% include
		image.html
		lightbox="true"
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -5,13 +5,31 @@ group: promotions
		toc: true
		---

		## Promotions in Codefresh GitOps
		Continuous Delivery (CD) is an essential practice in the Software Development Lifecycle (SDLC) that automates the release process, ensuring consistent and reliable deployment of application updates across environments. CD bridges the gap between development and operations, empowering teams to deliver changes to production with speed and confidence.

		A core element of CD is promotion - the process of advancing an application version through environments, such as from staging to production, based on predefined criteria or approvals. Promotion sequences ensure that only validated, stable versions of applications only validated, stable versions reach production, reducing risk with every release.

		## Getting started with promotions in GitOps

		Review these articles to begin with promotions in Codefresh GitOps:
		##### Walk through with quick starts
		Dive into [quick starts on promotions]({{site.baseurl}}/docs/gitops-quick-start/promotions/)<!--- ({{site.baseurl}}/docs/gitops-quick-start/)--> for step-by-step guides to get started efficiently.

		### Promotions with GitOps: The Codefresh advantage
		Watch this video to see a promotion in action:
		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Drag-and-drop Promotion](https://www.youtube.com/watch?v=4isYoutmRco&t=1s){:target="\_blank"}


		##### Understand the components and entities
		Explore [Promotion building blocks]({{site.baseurl}}/docs/promotions/promotion-components/) to learn about the key entities and how they fit together in the promotion process.

		##### Set up and configure promotions
		Follow the guidelines in [Promotions: Setup & configuration]({{site.baseurl}}/docs/promotions/create-promotion-sequence/) to configure, trigger, and monitor promotions.

		Watch this video to learn how to configure an automated Promotion Flow:
		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Promotion Flows](https://www.youtube.com/watch?v=M8G-AY7FIIg&t=76s){:target="\_blank"}

		## Promotions with GitOps: The Codefresh advantage
		Codefresh builds on the power of GitOps by fully integrating promotions into its framework, giving you enhanced visibility, control, and automation, with Git as the single source of truth.

		{% include
Expand DownExpand Up		@@ -54,7 +72,7 @@ max-width="65%"
		>NOTE
		You need Runtime version 0.13.4 or higher to support GitOps promotions. Ensure your runtime is updated to at least this version to access promotion features.

		### GitOps promotion entities
		## GitOps promotion entities
		Codefresh GitOps provides specialized functionality to streamline and automate the promotion process, ensuring consistency and control without the need for custom scripts. These features allow you to design predictable reusable delivery lifecycles across products and environments, with all the required validations, reducing operational overhead and manual errors.

		* Predefine properties to promote
Expand All		@@ -79,12 +97,7 @@ Codefresh GitOps provides specialized functionality to streamline and automate
		<!--- screenshot of yaml examples to differentiate and not overcrowd -->


		### Getting started with promotions in GitOps

		Review these articles to begin with GitOps promotions:
		* Walk through with quick starts: Dive into [quick starts on promotions]({{site.baseurl}}/docs/gitops-quick-start/promotions/)<!--- ({{site.baseurl}}/docs/gitops-quick-start/)--> for step-by-step guides to get started efficiently.
		* Understand the components and entities: Explore [Promotion building blocks]({{site.baseurl}}/docs/promotions/promotion-components/) to learn about the key entities and how they fit together in the promotion process.
		* Set up and configure promotions: Follow the guidelines in [Promotions: Setup & configuration]({{site.baseurl}}/docs/promotions/create-promotion-sequence/) to configure, trigger, and monitor promotions.



Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -7,10 +7,18 @@ toc: true

		Promotions are a key component of the continuous delivery (CD) process, enabling teams to control how software moves through various environments based on automated triggers or manual inputs.

		Codefresh GitOps supports automated promotion sceanrios tailored to various deployment models through Promotion Flows, triggered on predefined criteria, such as specific commit messages or changes in Git branches, allowing seamless and consistent updates across environments. See [Creating Promotion Flows](#{{site.baseurl}}/docs/promotions/promotion-flow/).
		Codefresh GitOps supports automated promotion scenarios tailored to various deployment models through Promotion Flows, triggered on predefined criteria, such as specific commit messages or changes in Git branches, allowing seamless and consistent updates across environments.

		Watch the video:
		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Promotion Flows](https://www.youtube.com/watch?v=M8G-AY7FIIg){:target="\_blank"}

		See also [Creating Promotion Flows](#{{site.baseurl}}/docs/promotions/promotion-flow/).

		Recognizing that some scenarios require on-demand control, Codefresh also provides manual promotion triggers to handle specific needs. Whether deploying a hotfix to production, promoting an entire product release, or testing code changes in a targeted environment, manual promotion options offer flexibility to meet these demands.

		Watch the video:
		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/}[Drag-and-drop Promotion](https://www.youtube.com/watch?v=4isYoutmRco&t=1s){:target="\_blank"}

		Manual promotion triggers provide different levels of control, accessible from distinct areas of the platform, enabling:

		* Single-environment promotion
Expand DownExpand Up		@@ -45,6 +53,7 @@ Each method is available only if your account administrator has assigned permiss
		Drag-and-drop the product to the target environment to promote changes, and customize the Promotion Settings to control promotion behavior for the environment.
		This method is useful to test changes within a specific environment. For example, QA teams wanting to test changes in staging or other internal environments.

		{::nomarkdown}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Drag-and-drop promotions](https://www.youtube.com/watch?v=4isYoutmRco){:target="\_blank"}


		##### Before you begin
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -63,5 +63,11 @@ ul > li {
		&:not([href^="https://g.codefresh.io/"]):not([href*="/docs/"]):not([href^="#"]){
		@include external-link("external-link");
		}

		&[href^="https://www.youtube.com/"] {
		&::after {
		display: none !important;
		}
		}
		}
		}