You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great tool however, I have hit an occasional problem.
When I run the action and the waiting action fails. if I re-run the parent action it immediately sees there has been a previous run with a failure and fails, without waiting for the second run.
The code I run is:
- name: Trigger Development Deployment
uses: benc-uk/[email protected]
with:
workflow: Deploy to PaaS
token: ${{ secrets.ACTIONS_API_ACCESS_TOKEN }}
inputs: '{"environment": "Development", "sha": "${{ github.sha }}"}'
ref: ${{github.ref}}
- name: Wait for Deployment to Development
uses: fountainhead/[email protected]
id: wait-for-deploy
with:
token: ${{ secrets.ACTIONS_API_ACCESS_TOKEN}}
checkName: Deploy Development
ref: ${{github.ref}}
Retrieving check runs named Deploy Development on DFE-Digital/get-into-teaching-api@refs/heads/master...
Retrieved 1 check runs named Deploy Development
Found a completed check with id 1644407390 and conclusion failure
Is there any chance of a flag that allows 'latest-run: true' so it ignores previous runs?
The text was updated successfully, but these errors were encountered:
By default, listForRef() in poll.ts returns the latest. However, I believe the problem is that without any delay before the call to listForRef(), at times the status from a previous run is returned. See #32 for a proposed solution.
Great tool however, I have hit an occasional problem.
When I run the action and the waiting action fails. if I re-run the parent action it immediately sees there has been a previous run with a failure and fails, without waiting for the second run.
The code I run is:
Retrieving check runs named Deploy Development on DFE-Digital/get-into-teaching-api@refs/heads/master...
Retrieved 1 check runs named Deploy Development
Found a completed check with id 1644407390 and conclusion failure
Is there any chance of a flag that allows 'latest-run: true' so it ignores previous runs?
The text was updated successfully, but these errors were encountered: