Merge branch 'main' into repo-sync

content/actions/deployment/deploying-to-amazon-elastic-container-service.md

@@ -21,9 +21,9 @@ shortTitle: Deploy to Amazon ECS
 
 ## Introduction
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when a release is created.
+This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when there is a push to the `main` branch.
 
-On every new release in your {% data variables.product.company_short %} repository, the {% data variables.product.prodname_actions %} workflow builds and pushes a new container image to Amazon ECR, and then deploys a new task definition to Amazon ECS.
+On every new push to `main` in your {% data variables.product.company_short %} repository, the {% data variables.product.prodname_actions %} workflow builds and pushes a new container image to Amazon ECR, and then deploys a new task definition to Amazon ECS.
 
 ## Prerequisites
 
@@ -85,8 +85,9 @@ Ensure that you provide your own values for all the variables in the `env` key o
 name: Deploy to Amazon ECS
 
 on:
-  release:
-    types: [ created ]
+  push:
+    branches:
+      - main
 
 env:
   AWS_REGION: MY_AWS_REGION                   # set this to your preferred AWS region, e.g. us-west-1

content/actions/deployment/deploying-to-azure-app-service.md

@@ -75,7 +75,7 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 
 Once you've completed the prerequisites, you can proceed with creating the workflow.
 
-The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when a release is created.
+The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when there is a push to the `main` branch.
 
 Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. You can also change `AZURE_WEBAPP_PACKAGE_PATH` if the path to your project is not the repository root and `NODE_VERSION` if you want to use a node version other than `10.x`.
 
@@ -85,8 +85,9 @@ Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 
 on:
-  release:
-    types: [created]
+  push:
+    branches:
+      - main
 
 env:
   AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name

content/actions/deployment/deploying-to-google-kubernetes-engine.md

@@ -21,7 +21,7 @@ shortTitle: Deploy to Google Kubernetes Engine
 
 ## Introduction
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when a release is created.
+This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when there is a push to the `main` branch.
 
 GKE is a managed Kubernetes cluster service from Google Cloud that can host your containerized workloads in the cloud or in your own datacenter. For more information, see [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine).
 
@@ -125,8 +125,9 @@ Under the `env` key, change the value of `GKE_CLUSTER` to the name of your clust
 name: Build and Deploy to GKE
 
 on:
-  release:
-    types: [created]
+  push:
+    branches:
+      - main
 
 env:
   PROJECT_ID: {% raw %}${{ secrets.GKE_PROJECT }}{% endraw %}

content/actions/deployment/deploying-with-github-actions.md

@@ -31,13 +31,12 @@ You should be familiar with the syntax for {% data variables.product.prodname_ac
 
 ## Triggering your deployment
 
-You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, `release`, and `workflow_dispatch`.
+You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, and `workflow_dispatch`.
 
 For example, a workflow with the following triggers runs whenever:
 
 - There is a push to the `main` branch.
 - A pull request targeting the `main` branch is opened, synchronized, or reopened.
-- A release is created.
 - Someone manually triggers it.
 
 ```yaml
@@ -48,9 +47,6 @@ on:
   pull_request:
     branches:
       - main
-  release:
-    types:
-      - created
   workflow_dispatch:
 ```