GitHub Deployments

KineticCafe/deployments is a fork of bobheadxi/deployments upgraded to support Node 20.

deployments is a GitHub Action for working painlessly with GitHub deployment statuses. Instead of exposing convoluted Action configuration that mirrors that of the GitHub API like some of the other available Actions do, this Action simply exposes a number of configurable, easy-to-use "steps" common to most deployment life cycles.

• Configuration
  • step: start
  • step: finish
  • step: deactivate-env
  • step: delete-env
• Debugging

A simple example:

on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: start deployment
        uses: KineticCafe/deployments@v1
        id: deployment
        with:
          step: start
          token: ${{ secrets.GITHUB_TOKEN }}
          env: release

      - name: do my deploy
        # ...

      - name: update deployment status
        uses: KineticCafe/deployments@v1
        if: always()
        with:
          step: finish
          token: ${{ secrets.GITHUB_TOKEN }}
          status: ${{ job.status }}
          env: ${{ steps.deployment.outputs.env }}
          deployment_id: ${{ steps.deployment.outputs.deployment_id }}

Configuration

The following inputs configuration options are for all steps:

Variable	Default	Purpose
step		One of start, finish, deactivate-env, or delete-env
token	${{ github.token }}	provide your ${{ github.token }} or ${{ secrets.GITHUB_TOKEN }} for API access
env		identifier for environment to deploy to (e.g. staging, prod, main)
repository	Current repository	target a specific repository for updates, e.g. owner/repo
logs	URL to GitHub commit checks	URL of your deployment logs
desc	GitHub-generated description	description for this deployment
ref	github.ref	Specify a particular git ref to use, (e.g. ${{ github.head_ref }})

step: start

This is best used on the push: { branches: [ ... ] } event, but you can also have release: { types: [ published ] } trigger this event. start should be followed by whatever deployment tasks you want to do, and it creates and marks a deployment as "started":

In addition to the core configuration, the following inputs are available:

Variable	Default	Purpose
deployment_id		Use an existing deployment instead of creating a new one (e.g. ${{ github.event.deployment.id }})
override	false	whether to mark existing deployments of this environment as inactive
auto_merge	false	Attempts to automatically merge the default branch into the requested ref, if it's behind the default branch.
required_contexts	''	The names of any status contexts to verify against, separated by newlines. To bypass checking entirely, pass a string ''
payload		JSON-formatted dictionary with extra information about the deployment
task	'deploy'	change the task associated with this deployment, can be any string

The following outputs are available:

Variable	Purpose
deployment_id	ID of created GitHub deployment
status_id	ID of created GitHub deployment status
env	name of configured environment

Simple Push Example

on:
  push:
    branches:
      - main

jobs:
  deploy:
    steps:
      - name: start deployment
        uses: KineticCafe/deployments@v1
        id: deployment
        with:
          step: start
          env: release

      - name: do my deploy
        # ...

Simple Pull Request Example

on:
  pull_request:

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: start deployment
        uses: KineticCafe/deployments@v1
        id: deployment
        with:
          step: start
          env: integration

      - name: do my deploy
        # ...

step: finish

This is best used after step: start and should follow whatever deployment tasks you want to do in the same workflow. finish marks an in-progress deployment as complete:

In addition to the core configuration, the following inputs are available:

Variable	Default	Purpose
status		provide the current deployment job status ${{ job.status }}
deployment_id		identifier for deployment to update (see outputs of step: start)
env_url		URL to view deployed environment
override	true	whether to manually mark existing deployments of this environment as inactive
auto_inactive	false	whether to let GitHub handle marking existing deployments of this environment as inactive (if and only if a new deployment succeeds).

Simple Example

# ...

jobs:
  deploy:
    steps:
      - name: start deployment
        # ... see previous example

      - name: do my deploy
        # ...

      - name: update deployment status
        uses: KineticCafe/deployments@v1
        if: always()
        with:
          step: finish
          token: ${{ secrets.GITHUB_TOKEN }}
          status: ${{ job.status }}
          env: ${{ steps.deployment.outputs.env }}
          deployment_id: ${{ steps.deployment.outputs.deployment_id }}

step: deactivate-env

This is best used on the pull_request: { types: [ closed ] } event, since GitHub does not seem to provide a event to detect when branches are deleted. This step can be used to automatically shut down deployments you create on pull requests and mark environments as destroyed:

Refer to the core configuration for available inputs.

Simple Example

on:
  pull_request:
    types: [closed]

jobs:
  prune:
    steps:
      # see https://dev.to/bobheadxi/branch-previews-with-google-app-engine-and-github-actions-3pco
      - name: extract branch name
        id: get_branch
        shell: bash
        env:
          PR_HEAD: ${{ github.head_ref }}
        run: echo "##[set-output name=branch;]$(echo ${PR_HEAD#refs/heads/} | tr / -)"

      - name: do my deployment shutdown
        # ...

      - name: mark environment as deactivated
        uses: KineticCafe/deployments@v1
        with:
          step: deactivate-env
          token: ${{ secrets.GITHUB_TOKEN }}
          env: ${{ steps.get_branch.outputs.branch }}
          desc: Environment was pruned

step: delete-env

This is the same as deactivate-env, except deletes the environment entirely. See step: deactivate-env for more details.

Note that the default GITHUB_TOKEN does not allow environment deletion - you have to set a personal access token with repo scope from an account with repo admin permissions and provide it in the token input.

Refer to the core configuration for available inputs.

Debugging

The argument debug: true can be provided to print arguments used by deployments and log debug information.

If you run into an problems or have any questions, feel free to open an issue!