"Umbraco CI/CD Flow" section on the Advanced page.
"Umbraco CI/CD Flow" section on the Advanced page.
Azure DevOps Repository
Configure pipeline with existing YAML file
Select Branch and Path
Pipeline variables in Azure DevOps
+{% endhint %}
+
+{% hint style="info" %}
+You can customize the names for the variables as you like, however, you then need to rename the affected variables in `azure-release-pipeline.yaml`.
+
+Check the references to the variables in the yaml files match the variable syntaxes in the created variable. Example: `umbracoCloudApiKey` = `UMBRACOCLOUDAPIKEY`.
+{% endhint %}
+
+When you click on "Save and Run" your first deployment will be triggered. Which means that Azure DevOps is set up with all the needed information to be able to deploy your Cloud project back to Umbraco Cloud.
+
+### Optional: Test the pipeline
+
+With everything set up, you may want to confirm that Umbraco Cloud reflects the changes you are sending via your pipeline.
+
+While working on your project locally, add a new Document type.
+
+* Commit the change to `main` branch (or `master` if you did not change the branch name) and push to your repository.
+* The pipeline starts to run
+* Once the pipeline is done log into Backoffice on your left-most environment in Umbraco Cloud
+* Go to the Settings section and see that your new Document type has been deployed
+
+## High level overview of the pipeline components
+
+The mentioned scripts are provided as a starting point. It is recommended that you familiarize yourself with the scripts and with documentation related to how to use Azure DevOps.
+
+The scripts demonstrates the following:
+
+* How to sync your Azure DevOps repository with the [left-most project environment](../../../../deployment/) in Umbraco Cloud
+* How to deploy changes to the left-most project environment in Umbraco Cloud
+
+### Main
+
+The `azure-release-pipeline.yaml` is the main pipeline, and is the one that will be triggered on a push to `main` branch. You can configure a different trigger behavior in this file.
+
+You can add your Build and Test stage between the `cloudSyncStage` and `cloudDeploymentStage` stages. Keep in mind that you do not need to retain the dotnet build artifact for upload later. The `cloudDeploymentStage` job will take care of packaging all your source code and upload to Umbraco Cloud.
+
+### Cloud-sync
+
+The `cloud-sync.yml` shows how you can sync your Azure DevOps repository with the left-most environment of your Cloud project. In this sample, it accepts any change from the API and applies and commits it back to the branch which triggered the pipeline. However the commit does not trigger the pipeline again.
+
+If you don't want the pipeline to commit back to the triggering branch, this is where you need to change the pipeline.
+
+### Cloud-deployment
+
+The `cloud-deployment.yml` shows how you can deploy your repository to the left-most environment of your Cloud project. The sample shows how to prepare for deployment, request the deployment and wait for cloud to finish.
+
+There are a couple of things here to be aware of:
+
+* We are overwriting the `.gitignore` file with `cloud.gitignore`. This is a way to accommodate your gitignore-needs when working locally. For instance you might want to ignore frontend builds, but you want them build and published to cloud.
+* We have a special `cloud.zipignore` file. This is a convenient way to tell the pipeline which files **not** to include when creating the zip package to send to cloud.
+
+{% hint style="info" %}
+If you have frontend assets that needs to be built (using npm/yarn or other tools), add the needed steps before `Zip Source Code`. This ensures that the fresh frontend assets will be part of the package to be sent to Umbraco Cloud.
+{% endhint %}
+
+## Further information
+
+* [Azure Pipelines Documentation](https://learn.microsoft.com/en-us/azure/devops/pipelines/)
diff --git a/umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/V1-github-actions.md b/umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/V1-github-actions.md
new file mode 100644
index 00000000000..2128b0e9ef3
--- /dev/null
+++ b/umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/V1-github-actions.md
@@ -0,0 +1,240 @@
+---
+hidden: true
+---
+
+# GitHub Actions
+
+Before setting up the pipeline in GitHub, make sure that the following steps from the [Configuring a CI/CD pipeline](./) are done:
+
+* Pick a Cloud project
+* Activate CI/CD Flow
+
+Next, you will need to define your pipeline in YAML and use it to interact with the Umbraco Cloud API.
+
+{% hint style="info" %}
+The Umbraco CI/CD Team has created a sample pipeline for GitHub Actions.
+
+The Scripts are provided as is. This means that the scripts will do the bare minimum for a pipeline that is utilizing the CI/CD flow.
+
+You'll need to adapt and integrate the script to fit your pipelines to gain the ability to do deployments to your Umbraco Cloud projects.
+
+The sample includes YAML files and custom Powershell and Bash scripts to interact with the Umbraco Cloud API.
+
+You can get the samples for both `Azure DevOps` and `GitHub Actions` from the [GitHub repository](https://github.com/umbraco/Umbraco.Cloud.CICDFlow.Samples).
+
+Samples that target the endpoints described here are located in the V1 folder.
+{% endhint %}
+
+{% hint style="warning" %}
+Please be aware that since this involves using your custom pipeline, any issues that arise will need to be resolved by you.
+{% endhint %}
+
+## Import Cloud project repository to GitHub
+
+Go to your repositories in GitHub and click on "New".
+
+* Create a new empty repository, and note down the clone URL.
+* Go to the Umbraco Cloud Portal and clone your cloud project down locally. [This article](../../../working-locally.md#cloning-an-umbraco-cloud-project) describes how you can find the clone URL.
+* Now working locally remove the Git Remote called `origin`, which points to Umbraco Cloud
+
+```sh
+git remote remove origin
+```
+
+* Optionally rename branch `master` to `main`
+
+```sh
+# optional step
+git branch -m main
+git symbolic-ref HEAD refs/heads/main
+```
+
+* Add a new remote called origin and pointing to the GitHub clone URL and push
+
+```sh
+git remote add origin https://github.com/{your-organization}/{your-repository}.git
+git push -u origin --all
+```
+
+Now we can move on to setting up a pipeline.
+
+## Set up GitHub repository variables
+
+The pipeline needs to know which Umbraco Cloud project to deploy to. In order to do this you will need the `Project ID` and the `API Key`. [This article](./#obtaining-the-project-id-and-api-key) describes how to get those values.
+
+* Now go to the repository in GitHub, and click on the Settings section.
+* Expand secrets and variables in the left-hand menu titled `Security` and click on `Actions`.
+
+ (1) (1) (1).png)
Security and Actions menu GitHub
GitHub Workflow permissions
Azure DevOps Repository
Pipeline variables in Azure DevOps