ServiceNow DevOps Change GitHub Action is billed for entire approval waiting time
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2023 03:57 AM
Hi All,
We are prototyping automated change request creation from out GitHub pipelines. We are using at the ServiceNow DevOps Change GitHub Action https://github.com/marketplace/actions/servicenow-devops-change-automation.
We have it all working fine with our GitHub talking to Service Now.
We wait for approval of the CR from service now before allowing the pipeline to continue. I noted that we are billed GitHub Actions time for the period of waiting for approval, in the example below the approval took 11 mins, and we were billed by GitHub for that wait time, see below.
In the 'real' world approvals could take hours or days depending on the number of approvals and availability of approvers, this would not be acceptable as cost.
Is there anyway around this busy billable wait when using the Change Github Action?
Thanks
Lee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2023 10:04 AM
Hi Lee,
This is a known issue that is being corrected through the new use of GitHub Actions Deployment Protection Rules. I believe this is being shipped in the next store update but I'll try to check and respond again here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2023 02:06 AM
@LeeCheetham As @Richard91 mentioned, this is resolved with GitHub feature, Deployment Protection Rules.
The support for GitHub Deployment Protection Rules was provided in 2.0 release of DevOps Change Velocity. Please try that and it is documented here, https://docs.servicenow.com/bundle/vancouver-devops/page/product/enterprise-dev-ops/concept/github-d...
Thanks
Senthil