Skip to main content
Knowledge Base

How do I prevent Gruntwork Pipelines from running in GitHub Actions?

Answer

When I create a new `_envcommon` file without any modules referencing it, Gruntwork Pipelines will still run in every applicable environment/account, even though there are no changes. How can I prevent this behavior without making changes to the Gruntwork-supported code? --- <ins datetime="2023-04-25T16:21:28Z"> <p><a href="https://support.gruntwork.io/hc/requests/110116">Tracked in ticket #110116</a></p> </ins>

Per [https://github.blog/changelog/2021-02-08-github-actions-skip-pull-request-and-push-workflows-with-skip-ci/](https://github.blog/changelog/2021-02-08-github-actions-skip-pull-request-and-push-workflows-with-skip-ci/): >February 8, 2021 GitHub Actions now supports skipping push and pull_request workflows by looking for some common keywords in your commit message. \ \ If any commit message in your push or the HEAD commit of your PR contains the strings [skip ci], [ci skip], [no ci], [skip actions], or [actions skip] workflows triggered on the push or pull_request events will be skipped. So whether you're opening a PR and committing or merging directly to a branch, you can use any of `[skip ci]`, `[ci skip]`, `[no ci]`, `[skip actions]`, or `[actions skip]` to prevent Gruntwork Pipelines, and any additional GitHub Actions you have configured, from running.