Expected — Waiting for status to be reported after commit

[aidan-melen]

The objective of this workflow is to format the terraform source code and automatically commit these new changes to the branch.

note the is simply a modification of the recommend hashicorp workflow

name: Terraform

on:
  push:
    branches:
      - main
  pull_request:

jobs:

  lint:
    name: Lint, Auto Format, and Validate
    runs-on: ubuntu-20.04
    steps:
      - name: Checkout
        uses: actions/checkout@master

      - name: Setup Terraform
        uses: hashicorp/setup-terraform@v1
        with:
          terraform_version: 0.13.5
          cli_config_credentials_hostname: 'example.org'
          cli_config_credentials_token: ${{ secrets.TF_API_TOKEN }}

      - name: Init
        id: init
        run: terraform init

      - name: Format
        id: format
        run: terraform fmt --recursive
      
      - name: Add and Commit Auto Format Changes
        uses: EndBug/add-and-commit@v7
        with:
          author_name: '@${{ github.actor }}'
          message: 'Auto Format Terraform code changes.'
          add: '.'

      - name: Validate
        id: validate
        run: terraform validate

Problem: The initial commit with the badly formatted code triggers this Lint, Auto Format, and Validate to run. Which will format the code and commit to the branch like we want. However, this new commit fails to retrigger the Lint, Auto Format, and Validate a second time. As a result, the Require Checks in the branch protection rule gets stuck waiting for the job to re-trigger from the auto commit, but it never does. Instead you just get this

Why is the job not re-triggering on the commit from this github action???

[EndBug]

The commit created by the action is not triggering further action runs because it has been made using the default GITHUB_TOKEN, which GitHub recognizes and ignores for CI runs
If you want it to trigger CI checks, you need to set up the repo with a custom PAT, you can do that with actions/checkout. My action uses the token the repo has been set up with, so there's no need to change any add-and-commit input.

Ref: https://github.com/EndBug/add-and-commit#tokens

Feel free to tell me if you need any further help!

[aidan-melen]

The commit created by the action is not triggering further action runs because it has been made using the default GITHUB_TOKEN, which GitHub recognizes and ignores for CI runs
If you want it to trigger CI checks, you need to set up the repo with a custom PAT, you can do that with actions/checkout. My action uses the token the repo has been set up with, so there's no need to change any add-and-commit input.

Ref: https://github.com/EndBug/add-and-commit#tokens

Feel free to tell me if you need any further help!

Awesome, that makes sense. I will give that a try! Thanks for the recommendation