# Release a Domain

<figure><img src="https://1175929715-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMXJauKOgXVlDwo5NJ6c%2Fuploads%2Fgit-blob-dad1b44230d2cbddaab01740e2ba7afe13419665%2Fimage%20(1)%20(1).png?alt=media" alt=""><figcaption><p>Release a domain workflow</p></figcaption></figure>

The above diagram describes the "Release a Domain" workflow. This workflow is triggered by creating an issue or by clicking the "Initiate Release" from the dashboard.

<figure><img src="https://1175929715-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMXJauKOgXVlDwo5NJ6c%2Fuploads%2Fgit-blob-babdd8ed572124d953a975e9486a22d359d1a7c6%2Finitiate-release_v2.gif?alt=media" alt=""><figcaption><p>Initiating a release from the sfops dashboard<br><br></p></figcaption></figure>

This workflow then proceeds to fetch all the environments that are marked with "**type:release"** and proceeds to execute a dry run of the command in parallel across all release environments. The output of the dry run will be available as a comment in the Github issue created. The team could have a final check on the deployment plan that will be executed by sfops before proceeding for the actual execution.

<figure><img src="https://1175929715-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMXJauKOgXVlDwo5NJ6c%2Fuploads%2Fgit-blob-c7dd47b5a20d7ad8e19323cb09a3dde594cd2371%2Fimage%20(2).png?alt=media" alt=""><figcaption></figcaption></figure>

The release environments typically is configured with "Required Reviewers" (<https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#required-reviewers>) and would need the respective environment owners to approve a release. Please note required reviewers are not required for the pre-release/ dry run check
