Skip to content

Latest commit

 

History

History
57 lines (37 loc) · 2.22 KB

README.md

File metadata and controls

57 lines (37 loc) · 2.22 KB
Raw

Consecutive Workflow Action

Make workflow runs run consecutively.

Create a comment here and delete it immediately and then go to the Actions tab to see how the second workflow run waits for the previous one.

Usage

jobs:
  consecutiveness:
    runs-on: ubuntu-latest
    steps:
    - uses: mktcode/consecutive-workflow-action@e2e008186aa210faacd68ec30f6ac236f7e2f435
      with:
        token: ${{ secrets.GITHUB_TOKEN }}

  # your other jobs
  something:
    runs-on: ubuntu-latest
    needs: [ consecutiveness ]
    steps:
    # ...

Security Notes:

Access Token

The token is needed to avoid rate limitation issues when performing API calls. I was thinking about making that optional but decided to just make you aware of the security risk and how to avoid it.

Please read this section in the docs before using some random action that asks for your secrets.

To use the latest version automatically, use the main branch.

- uses: mktcode/consecutive-workflow-action@main

I recommend using a commit hash instead though, like in the usage example.

Workflow Permissions

It's always a good idea to limit permissions to the required minimum. To read information about previous runs, the workflow needs at least the actions: read permission.

Alternatives

I also found these actions, which might better suit your needs:

Their purpose is slightly different. You can wait for certain checks to pass and therefore you can specify a certain ref and you can wait for runs of different workflows.

My action does only one thing: It forces runs of the same workflow to run in consecutive order.

I needed this because I let my workflows push to the repo a lot, which fails when one run pushes in between checkout and push in another run.