---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# GitHub Deployment Gates for ServiceNow DevOps Change

# GitHub Deployment Gates for ServiceNow DevOps Change {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Use the GitHub Deployment Gate capability to decide on whether a new deployment should proceed or halt.

## Before you begin

GitHub deployment gates are supported only if you have connected your GitHub instance with Oauth 2.0 credentials for GitHub Apps using the JWT bearer token. For more information, see [OAuth 2.0 credentials for GitHub Apps - JWT](https://www.servicenow.com/docs/pYj7RzmHaIyI3F~v8Dkv6Q#dev-ops-github-apps-oath-jwt "Perform the following steps to integrate your GitHub Apps using the JWT bearer token.").

By default, the Deployment protection rules section is available for environments in all the repositories selected in the installed GitHub App.

Role required: Permission to create environments in GitHub

## Procedure

1. Navigate to Settings \> Environments from a repository and click New environment to create an environment.
2. In the Deployment protection rules section, select the installed GitHub App name, and select Save protection rules.
3. Add the ServiceNow DevOps Change Automation custom action at the step level (for example, changeRequest job in workflow/yaml file) in a pipeline job to create the change for deployment gates.  
   The deployment-gate parameter must be added in the following JSON format.  

       '{"environment":"deployment_gate","jobName":"Deploy"}'

   Here environment key value is the environment created with deployment protection rules, and jobName key value is the deployment job created in the workflow/yaml file with dependency on the change request job configured with the ServiceNow DevOps Change Automation custom action.

   When the deployment gate specific workflow/yaml file is run in GitHub Actions, the details like change number, change url, and status will be displayed once the change request is created in ServiceNow.

   The details like change comments, approved by, approved on, and status are logged in the GitHub tool after the workflow run is resumed from ServiceNow, i.e. when change request is approved and the change request
   state is updated to Implement in ServiceNow.