Endless cycle of github actions initiated by a build #74772

iamshreeram · 2023-11-09T05:43:45Z

iamshreeram
Nov 9, 2023

Select Topic Area

Question

Body

I have a repo for which github actions is configured.

The action involves code validation and the generation of a PDF file as a result.
The GH action then publishes the file to the main branch of a separate repository, all while committing the PDF file to the main branch of the original repository where the action was initiated.
Since the commit is made to the same branch, the GH action is triggered once more, causing the cycle to repeat from step 1.

This continuous loop of github actions is persisting. Is there any possible solution? Note: I have not been able to include an if condition to halt the build if the GH action is triggered by a different user, on a different branch, or by a different actor. Nevertheless, the GH action employs my own ID and token to commit the PDF file.

      - name: Get current branch name
        run: echo "BRANCH=${GITHUB_REF#refs/heads/}" >> $GITHUB_ENV
        
      - name: Check if workflow is triggered by the same repository push
        run: |
          if [[ $BRANCH = "main" && ${{ github.actor }} = "your-username" ]]; then
            echo "Skipping workflow run triggered by the same repository."
            exit 0
          fi

      - name: Verify commit author
        run: |
          COMMIT_AUTHOR=$(git --no-pager log -1 --pretty=format:'%an')
          COMMIT_COMMITTER=$(git --no-pager log -1 --pretty=format:'%cn')

          if [[ "$COMMIT_AUTHOR" == "GitHub Actions"* || "$COMMIT_COMMITTER" == "GitHub Actions"* ]]; then
            echo "Commit made by GitHub Actions workflow"
          else
            echo "Commit made by user"
          fi

Is there any other condition to check if the commit is triggered by GH action based on which I can stop the infinite loop ?

Answered by ev1sl

Nov 12, 2023

To prevent a GitHub Actions workflow from triggering itself in an infinite loop, you can use conditional checks within your workflow to determine if the commit was made by a GitHub Actions bot or by another user. If the commit was made by the bot, you can skip the rest of the job.

Here is a common approach using the GITHUB_ACTOR and github.event contexts:

jobs:
  build:
    runs-on: ubuntu-latest
    if: ${{ github.actor != 'github-actions[bot]' && github.event_name != 'push' || github.event.pusher.name != 'github-actions[bot]' }}
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      # Your other steps...

In this example:

github.actor provides the name of the pe…

View full answer

ev1sl · 2023-11-12T16:28:57Z

ev1sl
Nov 12, 2023

To prevent a GitHub Actions workflow from triggering itself in an infinite loop, you can use conditional checks within your workflow to determine if the commit was made by a GitHub Actions bot or by another user. If the commit was made by the bot, you can skip the rest of the job.

Here is a common approach using the GITHUB_ACTOR and github.event contexts:

jobs:
  build:
    runs-on: ubuntu-latest
    if: ${{ github.actor != 'github-actions[bot]' && github.event_name != 'push' || github.event.pusher.name != 'github-actions[bot]' }}
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      # Your other steps...

In this example:

github.actor provides the name of the person or app that initiated the workflow. If this is 'github-actions[bot]', then it means the workflow was triggered by GitHub Actions.
github.event_name checks the type of event that triggered the workflow. If it's a 'push' event, you can further check who the pusher was.
github.event.pusher.name can check the name of the user who pushed.
You've mentioned that you're using your own ID and token to commit the PDF file, which means the actor for the commit will be your username, not 'github-actions[bot]'. In this case, you need to use a different method, such as checking for a specific commit message that you set when the action commits the PDF file.

Here's an example of how you can skip a job if the last commit message contains a specific keyword (like [skip ci] or some unique identifier):

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Check last commit message
        id: commit-message
        run: echo "COMMIT_MESSAGE=$(git log -1 --pretty=format:'%s')" >> $GITHUB_ENV

      - name: Skip if commit is automated
        if: contains(env.COMMIT_MESSAGE, '[skip ci]')
        run: |
          echo "Automated commit detected - skipping job"
          exit 0

  # Your other steps...

In this setup:

The first step is to extract the last commit message and store it in an environment variable.
The second step uses an if condition to check if the commit message contains the [skip ci] keyword.
If the keyword is present, the step will print a message and then call exit 0, which successfully ends the current job without failing the workflow.
You would need to make sure that when the GitHub Action commits the PDF file, it includes this specific keyword in the commit message.

23 replies

lastepages23-code Dec 30, 2025

To prevent a GitHub Actions workflow from triggering itself in an infinite loop, you can use conditional checks within your workflow to determine if the commit was made by a GitHub Actions bot or by another user. If the commit was made by the bot, you can skip the rest of the job.

Here is a common approach using the GITHUB_ACTOR and github.event contexts:
jobs:
  build:
    runs-on: ubuntu-latest
    if: ${{ github.actor != 'github-actions[bot]' && github.event_name != 'push' || github.event.pusher.name != 'github-actions[bot]' }}
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      # Your other steps...
In this example:

github.actor provides the name of the person or app that initiated the workflow. If this is 'github-actions[bot]', then it means the workflow was triggered by GitHub Actions. github.event_name checks the type of event that triggered the workflow. If it's a 'push' event, you can further check who the pusher was. github.event.pusher.name can check the name of the user who pushed. You've mentioned that you're using your own ID and token to commit the PDF file, which means the actor for the commit will be your username, not 'github-actions[bot]'. In this case, you need to use a different method, such as checking for a specific commit message that you set when the action commits the PDF file.

Here's an example of how you can skip a job if the last commit message contains a specific keyword (like [skip ci] or some unique identifier):
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Check last commit message
        id: commit-message
        run: echo "COMMIT_MESSAGE=$(git log -1 --pretty=format:'%s')" >> $GITHUB_ENV

      - name: Skip if commit is automated
        if: contains(env.COMMIT_MESSAGE, '[skip ci]')
        run: |
          echo "Automated commit detected - skipping job"
          exit 0
  # Your other steps...
In this setup:

The first step is to extract the last commit message and store it in an environment variable. The second step uses an if condition to check if the commit message contains the [skip ci] keyword. If the keyword is present, the step will print a message and then call exit 0, which successfully ends the current job without failing the workflow. You would need to make sure that when the GitHub Action commits the PDF file, it includes this specific keyword in the commit message.

souihci0805-netizen Feb 9, 2026

zahernashwan Feb 15, 2026

To prevent a GitHub Actions workflow from triggering itself in an infinite loop, you can use conditional checks within your workflow to determine if the commit was made by a GitHub Actions bot or by another user. If the commit was made by the bot, you can skip the rest of the job.

Here is a common approach using the GITHUB_ACTOR and github.event contexts:
jobs:
  build:
    runs-on: ubuntu-latest
    if: ${{ github.actor != 'github-actions[bot]' && github.event_name != 'push' || github.event.pusher.name != 'github-actions[bot]' }}
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      # Your other steps...
In this example:

github.actor provides the name of the person or app that initiated the workflow. If this is 'github-actions[bot]', then it means the workflow was triggered by GitHub Actions. github.event_name checks the type of event that triggered the workflow. If it's a 'push' event, you can further check who the pusher was. github.event.pusher.name can check the name of the user who pushed. You've mentioned that you're using your own ID and token to commit the PDF file, which means the actor for the commit will be your username, not 'github-actions[bot]'. In this case, you need to use a different method, such as checking for a specific commit message that you set when the action commits the PDF file.

Here's an example of how you can skip a job if the last commit message contains a specific keyword (like [skip ci] or some unique identifier):
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Check last commit message
        id: commit-message
        run: echo "COMMIT_MESSAGE=$(git log -1 --pretty=format:'%s')" >> $GITHUB_ENV

      - name: Skip if commit is automated
        if: contains(env.COMMIT_MESSAGE, '[skip ci]')
        run: |
          echo "Automated commit detected - skipping job"
          exit 0
  # Your other steps...
In this setup:

The first step is to extract the last commit message and store it in an environment variable. The second step uses an if condition to check if the commit message contains the [skip ci] keyword. If the keyword is present, the step will print a message and then call exit 0, which successfully ends the current job without failing the workflow. You would need to make sure that when the GitHub Action commits the PDF file, it includes this specific keyword in the commit message.

ck880611 Feb 23, 2026

เพื่อป้องกันไม่ให้เวิร์กโฟลว์ GitHub Actions ทำงานวนซ้ำไม่รู้จบ คุณสามารถใช้การตรวจสอบเงื่อนไขภายในเวิร์กโฟลว์เพื่อตรวจสอบว่าการคอมมิตนั้นทำโดยบอท GitHub Actions หรือโดยผู้ใช้รายอื่น หากการคอมมิตนั้นทำโดยบอท คุณสามารถข้ามส่วนที่เหลือของเวิร์กโฟลว์ได้

ต่อไปนี้เป็นแนวทางทั่วไปที่ใช้บริบท GITHUB_ACTOR และ github.event:
jobs:
  build:
    runs-on: ubuntu-latest
    if: ${{ github.actor != 'github-actions[bot]' && github.event_name != 'push' || github.event.pusher.name != 'github-actions[bot]' }}
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      # Your other steps...
ในตัวอย่างนี้:

github.actor ระบุชื่อของบุคคลหรือแอปที่เริ่มต้นเวิร์กโฟลว์ หากเป็น 'github-actions[bot]' แสดงว่าเวิร์กโฟลว์ถูกเรียกใช้งานโดย GitHub Actions github.event_name ตรวจสอบประเภทของเหตุการณ์ที่เรียกใช้งานเวิร์กโฟลว์ หากเป็นเหตุการณ์ 'push' คุณสามารถตรวจสอบเพิ่มเติมได้ว่าใครเป็นผู้ส่ง push github.event.pusher.name สามารถตรวจสอบชื่อผู้ใช้ที่ส่ง push ได้ คุณได้กล่าวว่าคุณใช้ ID และโทเค็นของคุณเองในการ commit ไฟล์ PDF ซึ่งหมายความว่า actor สำหรับการ commit จะเป็นชื่อผู้ใช้ของคุณ ไม่ใช่ 'github-actions[bot]' ในกรณีนี้ คุณต้องใช้วิธีอื่น เช่น ตรวจสอบข้อความ commit เฉพาะที่คุณตั้งค่าไว้เมื่อ action commit ไฟล์ PDF

ต่อไปนี้เป็นตัวอย่างวิธีการข้ามงานหากข้อความคอมมิตล่าสุดมีคำหลักเฉพาะ (เช่น [skip ci] หรือตัวระบุเฉพาะบางอย่าง):
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Check last commit message
        id: commit-message
        run: echo "COMMIT_MESSAGE=$(git log -1 --pretty=format:'%s')" >> $GITHUB_ENV

      - name: Skip if commit is automated
        if: contains(env.COMMIT_MESSAGE, '[skip ci]')
        run: |
          echo "Automated commit detected - skipping job"
          exit 0
  # Your other steps...
ในการตั้งค่านี้:

ขั้นตอนแรกคือการดึงข้อความคอมมิตล่าสุดออกมาและเก็บไว้ในตัวแปรสภาพแวดล้อม ขั้นตอนที่สองใช้เงื่อนไข if เพื่อตรวจสอบว่าข้อความคอมมิตมีคำว่า [skip ci] หรือไม่ ถ้ามีคำนี้ ขั้นตอนนี้จะแสดงข้อความแล้วเรียก exit 0 ซึ่งจะสิ้นสุดงานปัจจุบันได้สำเร็จโดยไม่ทำให้เวิร์กโฟลว์ล้มเหลว คุณต้องตรวจสอบให้แน่ใจว่าเมื่อ GitHub Action คอมมิตไฟล์ PDF แล้ว ข้อความคอมมิตจะต้องมีคำนี้รวมอยู่ด้วย

https://support.github.com

souihci0805-netizen Feb 23, 2026

ok

iamshreeram · 2023-11-14T16:34:57Z

iamshreeram
Nov 14, 2023
Author

@ev1sl , thanks. that works!

3 replies

This comment was marked as off-topic.

Sign in to view

Semsemq May 14, 2025

👍🏻

Ascalad Feb 23, 2026

@ev1slممنون. جواب داد!

Thank you, I will use your instructions and explanations in my workflow, thank you.

suzaku · 2024-07-17T09:33:07Z

suzaku
Jul 17, 2024

I tried to reproduce a dead loop like this but failed: https://github.com/suzaku/github-actor-playground/blob/main/.github/workflows/blank.yml#L32-L37
The push that happened inside the action seems to be ignored: https://github.com/suzaku/github-actor-playground/actions
Any idea what's different?

4 replies

assignUser Jul 17, 2024

publishes the file to the main branch of a separate repository

This means they are using a PAT and not the built in GITHUB_TOKEN but you are using the default token which explicitly does not trigger CI events when used for pushing (to prevent endless loops ^^) https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow

1463389 Mar 3, 2025

jobs:
build:
runs-on: ubuntu-latest
if: ${{ github.actor != 'github-actions[bot]' && github.event_name != 'push' || github.event.pusher.name != 'github-actions[bot]' }}
steps:
- name: Checkout code
uses: actions/checkout@v2

  # Your other steps...

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

ghost · 2024-10-07T11:32:03Z

ghost
Oct 7, 2024

``

0 replies

SakornSaiprapan · 2024-11-09T08:25:04Z

SakornSaiprapan
Nov 9, 2024

Select Topic Area

Question

Body

I have a repo for which github actions is configured.

The action involves code validation and the generation of a PDF file as a result.

The GH action then publishes the file to the main branch of a separate repository, all while committing the PDF file to the main branch of the original repository where the action was initiated.

Since the commit is made to the same branch, the GH action is triggered once more, causing the cycle to repeat from step 1.

This continuous loop of github actions is persisting. Is there any possible solution? Note: I have not been able to include an if condition to halt the build if the GH action is triggered by a different user, on a different branch, or by a different actor. Nevertheless, the GH action employs my own ID and token to commit the PDF file.
      - name: Get current branch name
        run: echo "BRANCH=${GITHUB_REF#refs/heads/}" >> $GITHUB_ENV
        
      - name: Check if workflow is triggered by the same repository push
        run: |
          if [[ $BRANCH = "main" && ${{ github.actor }} = "your-username" ]]; then
            echo "Skipping workflow run triggered by the same repository."
            exit 0
          fi

      - name: Verify commit author
        run: |
          COMMIT_AUTHOR=$(git --no-pager log -1 --pretty=format:'%an')
          COMMIT_COMMITTER=$(git --no-pager log -1 --pretty=format:'%cn')

          if [[ "$COMMIT_AUTHOR" == "GitHub Actions"* || "$COMMIT_COMMITTER" == "GitHub Actions"* ]]; then
            echo "Commit made by GitHub Actions workflow"
          else
            echo "Commit made by user"
          fi
Is there any other condition to check if the commit is triggered by GH action based on which I can stop the infinite loop ?

1 reply

mdlassu Apr 15, 2025

  - name: Get current branch name
    run: echo "BRANCH=${GITHUB_REF#refs/heads/}" >> $GITHUB_ENV
    
  - name: Check if workflow is triggered by the same repository push
    run: |
      if [[ $BRANCH = "main" && ${{ github.actor }} = "your-username" ]]; then
        echo "Skipping workflow run triggered by the same repository."
        exit 0
      fi

  - name: Verify commit author
    run: |
      COMMIT_AUTHOR=$(git --no-pager log -1 --pretty=format:'%an')
      COMMIT_COMMITTER=$(git --no-pager log -1 --pretty=format:'%cn')

      if [[ "$COMMIT_AUTHOR" == "GitHub Actions"* || "$COMMIT_COMMITTER" == "GitHub Actions"* ]]; then
        echo "Commit made by GitHub Actions workflow"
      else
        echo "Commit made by user"
      fi

mdlassu · 2025-04-15T21:10:33Z

mdlassu Apr 15, 2025

jobs:

build:

runs-on: ubuntu-latest

steps:

  - name: Checkout code

    uses: actions/checkout@v2



  - name: Check last commit message

    id: commit-message

    run: echo "COMMIT_MESSAGE=$(git log -1 --pretty=format:'%s')" >> $GITHUB_ENV



  - name: Skip if commit is automated

    if: contains(env.COMMIT_MESSAGE, '[skip ci]')

    run: |

      echo "Automated commit detected - skipping job"

      exit 0jobs:

build:

runs-on: ubuntu-latest

if: ${{ github.actor != 'github-actions[bot]' && github.event_name != 'push' || github.event.pusher.name != 'github-actions[bot]' }}

steps:

  - name: Checkout code

    uses: actions/checkout@v2



  # Your other steps...

zwanski2019 · 2025-02-21T20:34:53Z

zwanski2019
Feb 21, 2025

Hi @iamshreeram,

To prevent the infinite loop caused by commits from your GitHub Action, add a conditional check to skip the workflow when the commit is made by the GitHub Actions bot itself:

Option 1: Filter by actor in the workflow step
Add this to your workflow YAML for the commit step:

- name: Commit PDF  
  if: github.event_name == 'push' && github.actor != 'github-actions[bot]'  
  run: |  
    git commit -m "Add generated PDF"  
    git push

Option 2: Skip CI with commit message
Add [skip ci] to your automated commit message:

git commit -m "Update PDF [skip ci]"

Option 3: Use a PAT from a bot account
Replace GITHUB_TOKEN with a Personal Access Token (PAT) from a dedicated bot account (e.g., your-bot-user) and filter by actor:

if: github.actor == 'your-bot-user'

GitHub Actions skips workflows triggered by the default GITHUB_TOKEN if the commit is made by github-actions[bot], but explicit filtering ensures reliability.

For more details: GitHub Docs on Skipping Workflows.

Let me know if you need more help!

3 replies

newlyborn25 · 2025-04-16T08:45:54Z

newlyborn25
Apr 16, 2025

http://github.event.pusher.name/

…

On Wed, 16 Apr 2025, 02:11 md lassu, ***@***.***> wrote: jobs: build: runs-on: ubuntu-latest steps: - name: Checkout code uses: ***@***.*** - name: Check last commit message id: commit-message run: echo "COMMIT_MESSAGE=$(git log -1 --pretty=format:'%s')" >> $GITHUB_ENV - name: Skip if commit is automated if: contains(env.COMMIT_MESSAGE, '[skip ci]') run: | echo "Automated commit detected - skipping job" exit 0jobs: build: runs-on: ubuntu-latest if: ${{ github.actor != 'github-actions[bot]' && github.event_name != 'push' || github.event.pusher.name != 'github-actions[bot]' }} steps: - name: Checkout code uses: ***@***.*** # Your other steps... — Reply to this email directly, view it on GitHub <#74772 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BRERO6GUWHJPVTED2GHFPMT2ZVYWHAVCNFSM6AAAAABLAHSKHGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOBUG4YDIMQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

0 replies

Boksh88 · 2025-07-02T03:46:18Z

Boksh88
Jul 2, 2025

Your other steps... # Your other steps...

0 replies

Francky5135 · 2025-07-28T01:33:11Z

Francky5135
Jul 28, 2025

Sélectionnez le domaine thématique

Question

Corps

J'ai un dépôt pour lequel les actions github sont configurées.

L'action implique la validation du code et la génération d'un fichier PDF en conséquence.

L'action GH publie ensuite le fichier dans la branche principale d'un référentiel distinct, tout en validant le fichier PDF dans la branche principale du référentiel d'origine où l'action a été initiée.

Étant donné que la validation est effectuée sur la même branche, l'action GH est déclenchée une fois de plus, ce qui entraîne la répétition du cycle à partir de l'étape 1.

Cette boucle continue d'actions GitHub persiste. Existe-t-il une solution ? Remarque : je n'ai pas pu inclure de condition « if » pour interrompre la compilation si l'action GH est déclenchée par un autre utilisateur, sur une autre branche ou par un autre acteur. Néanmoins, l'action GH utilise mon propre identifiant et mon jeton pour valider le fichier PDF.
      - name: Get current branch name
        run: echo "BRANCH=${GITHUB_REF#refs/heads/}" >> $GITHUB_ENV
        
      - name: Check if workflow is triggered by the same repository push
        run: |
          if [[ $BRANCH = "main" && ${{ github.actor }} = "your-username" ]]; then
            echo "Skipping workflow run triggered by the same repository."
            exit 0
          fi

      - name: Verify commit author
        run: |
          COMMIT_AUTHOR=$(git --no-pager log -1 --pretty=format:'%an')
          COMMIT_COMMITTER=$(git --no-pager log -1 --pretty=format:'%cn')

          if [[ "$COMMIT_AUTHOR" == "GitHub Actions"* || "$COMMIT_COMMITTER" == "GitHub Actions"* ]]; then
            echo "Commit made by GitHub Actions workflow"
          else
            echo "Commit made by user"
          fi
Existe-t-il une autre condition pour vérifier si la validation est déclenchée par l'action GH sur la base de laquelle je peux arrêter la boucle infinie ?

0 replies

lhcchcys-oss · 2025-08-12T05:53:06Z

lhcchcys-oss
Aug 12, 2025

{"version":"1.0.1","github_sha":"a4dbe621634a06596f5a929b9caa12d00e344844"}

0 replies

lhcchcys-oss · 2025-08-12T05:53:19Z

lhcchcys-oss
Aug 12, 2025

{"version":"1.0.1","github_sha":"a4dbe621634a06596f5a929b9caa12d00e344844"}``

0 replies

elyanero · 2025-09-04T02:06:03Z

elyanero
Sep 4, 2025

jobs:

build:
runs-on: ubuntu-latest
if: ${{ github.actor != 'github-actions[bot]' && github.event_name != 'push' || github.event.pusher.name != 'github-actions[bot]' }}
steps:
- name: Checkout code
uses: actions/checkout@v2

  # Your other steps...

1 reply

faisalsheiko986-png Nov 17, 2025

  - name: Get current branch name
    run: echo "BRANCH=${GITHUB_REF#refs/heads/}" >> $GITHUB_ENV
    
  - name: Check if workflow is triggered by the same repository push
    run: |
      if [[ $BRANCH = "main" && ${{ github.actor }} = "your-username" ]]; then
        echo "Skipping workflow run triggered by the same repository."
        exit 0
      fi

  - name: Verify commit author
    run: |
      COMMIT_AUTHOR=$(git --no-pager log -1 --pretty=format:'%an')
      COMMIT_COMMITTER=$(git --no-pager log -1 --pretty=format:'%cn')

      if [[ "$COMMIT_AUTHOR" == "GitHub Actions"* || "$COMMIT_COMMITTER" == "GitHub Actions"* ]]; then
        echo "Commit made by GitHub Actions workflow"
      else
        echo "Commit made by user"
      ### **fi__**

Maybe778 · 2025-11-30T11:23:00Z

Maybe778
Nov 30, 2025

Select Topic Area

Question

Body

I have a repo for which github actions is configured.

The action involves code validation and the generation of a PDF file as a result.

The GH action then publishes the file to the main branch of a separate repository, all while committing the PDF file to the main branch of the original repository where the action was initiated.

Since the commit is made to the same branch, the GH action is triggered once more, causing the cycle to repeat from step 1.

This continuous loop of github actions is persisting. Is there any possible solution? Note: I have not been able to include an if condition to halt the build if the GH action is triggered by a different user, on a different branch, or by a different actor. Nevertheless, the GH action employs my own ID and token to commit the PDF file.
      - name: Get current branch name
        run: echo "BRANCH=${GITHUB_REF#refs/heads/}" >> $GITHUB_ENV
        
      - name: Check if workflow is triggered by the same repository push
        run: |
          if [[ $BRANCH = "main" && ${{ github.actor }} = "your-username" ]]; then
            echo "Skipping workflow run triggered by the same repository."
            exit 0
          fi

      - name: Verify commit author
        run: |
          COMMIT_AUTHOR=$(git --no-pager log -1 --pretty=format:'%an')
          COMMIT_COMMITTER=$(git --no-pager log -1 --pretty=format:'%cn')

          if [[ "$COMMIT_AUTHOR" == "GitHub Actions"* || "$COMMIT_COMMITTER" == "GitHub Actions"* ]]; then
            echo "Commit made by GitHub Actions workflow"
          else
            echo "Commit made by user"
          fi
Is there any other condition to check if the commit is triggered by GH action based on which I can stop the infinite loop ?

0 replies

babaYaga666999 · 2025-12-04T03:54:04Z

babaYaga666999
Dec 4, 2025

http://github.event.pusher.name/

On Wed, 16 Apr 2025, 02:11 md lassu, @.***> wrote:

jobs:

build:

runs-on: ubuntu-latest

steps:

name: Checkout code
uses: ***@***.***
name: Check last commit message
id: commit-message
run: echo "COMMIT_MESSAGE=$(git log -1 --pretty=format:'%s')" >> $GITHUB_ENV
name: Skip if commit is automated
if: contains(env.COMMIT_MESSAGE, '[skip ci]')
run: |
  echo "Automated commit detected - skipping job"
  exit 0jobs:
build:

runs-on: ubuntu-latest

if: ${{ github.actor != 'github-actions[bot]' && github.event_name != 'push' || github.event.pusher.name != 'github-actions[bot]' }}

steps:

name: Checkout code
uses: ***@***.***
Your other steps...

—

Reply to this email directly, view it on GitHub

https://github.com/orgs/community/discussions/74772#discussioncomment-12847042,

or unsubscribe

https://github.com/notifications/unsubscribe-auth/BRERO6GUWHJPVTED2GHFPMT2ZVYWHAVCNFSM6AAAAABLAHSKHGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOBUG4YDIMQ

.

You are receiving this because you are subscribed to this thread.Message

ID: @.***

com>

0 replies

sifouchemam-source · 2026-01-12T21:41:57Z

sifouchemam-source
Jan 12, 2026

⏱️ Temps estimé : 15 minutes

Résultat : Vous aurez :

✅ Un compte GitHub sifouchemam
✅ Un dépôt avec votre code
✅ Un profil GitHub professionnel
✅ Votre application Streamlit liée à votre GitHub
✅ Une présence en ligne cohérente

🚨 Si le username "sifouchemam" est déjà pris :

Essayez ces variations :

sifou-chemam
sifouchemam-dev
sifouchemam-os
chemam-sifou

Commencez maintenant par l'étape 1 (github.com/signup), puis revenez si vous avez des questions spécifiques.

1 reply

souihci0805-netizen Feb 23, 2026

ok

Ascalad · 2026-02-17T03:02:17Z

Ascalad
Feb 17, 2026

Pull request and add workflow and GitHub documentation

1 reply

souihci0805-netizen Feb 23, 2026

ok

ARCH-angel93 · 2026-03-02T01:48:39Z

ARCH-angel93
Mar 2, 2026

Don't use CSS or visual like implementations, one cannot actually imply a visual distribution of points on a variance of actions, it would require graphic design related factors. Unless it was exact to a project a little markdown explanation or pdf inclusion of an example or visual thematic look or feel, perhaps charts or statements of outcomes, while this can provide a framework, but there must be a formative process of including how a user produces a pdf within its own performance, eg. steps for the format of files in documentation transfer with or without safety templates in a basic on non-basic making.

0 replies

ARCH-angel93 · 2026-03-02T01:50:11Z

ARCH-angel93
Mar 2, 2026

applying a end of cycle at the completion result would be lawful. or lawsuit or illicit behavior can breach pdf related materials and processes Ings.

1 reply

ganesh1633 Mar 12, 2026

nice

su9org · 2026-03-17T03:27:51Z

su9org
Mar 17, 2026

0 replies

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

Endless cycle of github actions initiated by a build #74772

Uh oh!

Select Topic Area

Body

Replies: 33 comments · 55 replies

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

iamshreeram Nov 14, 2023 Author

This comment was marked as off-topic.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

This comment was marked as off-topic.

This comment was marked as off-topic.

Uh oh!

This comment was marked as off-topic.

This comment was marked as off-topic.

Uh oh!

Select Topic Area

Body

Uh oh!

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

Uh oh!

This comment was marked as off-topic.

Uh oh!

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

Uh oh!

Uh oh!

Your other steps... # Your other steps...

Uh oh!

Sélectionnez le domaine thématique

Corps

This comment was marked as spam.

This comment was marked as off-topic.

Uh oh!

Uh oh!

Uh oh!

jobs:

Uh oh!

This comment was marked as off-topic.

Uh oh!

Replies: 33 comments 55 replies

iamshreeram
Nov 14, 2023
Author