Figure out a way to prevent pipelines from triggering multiple times on a PR

[staylorTT]

Currently this can be done manually via Github -> Actions -> On PR -> click … on your pipeline -> cancel run. This will help prevent backlog pipeline runs for everyone.

Look to see if there is a way to automate this to avoid clogging up the pipeline.

[vmilosevic]

There is no way to prevent pipelines from triggering multiple times. What we can do is to set a policy to cancel previously triggered runs, or to switch to manual triggering workflows.

Concurrency

GitHub Actions has a concurrency feature that can automatically cancel previous runs of the same workflow for a PR.
https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs
We can add concurrency to our PR workflow to implement the policy where new PR runs cancel all previously triggered runs with the same key.
We can use name to cancel all previous runs for the same branch

jobs:
  build:
    concurrency:
      group: ${{ github.workflow }}-${{ github.ref }}
      cancel-in-progress: true

Manual trigger

We can remove automatic triggering of workflows on PR, and have developers manually trigger them when they are ready to test. This can be triggered from Web UI ar using GH CLI tool

https://github.com/tenstorrent/tt-forge-internal/wiki/CI-CD-Guide#manually-trigger-workflow-runs

Skip CI

Also, there is an option for us to keep the automatic trigger, but control the workflow runs using the commit message. If you include [skip ci] string in the commit message workflows wont trigger automatically. Once developer is ready to ready to test, removing the commit message will enable the workflows

https://github.com/tenstorrent/tt-forge-internal/wiki/CI-CD-Guide#skip-workflow-runs