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
Currently, the lint, validate and convert action runs when a commit is made into a PR. If two commits are made in close sequence then two actions can be launched, when only the latter needs to complete.
This can cause the second action to fail in the commit phase of the conversion job as it seems that there are unstashed changes from when the first job overwrote the JSON-LD.
We can use GitHub actions concurrency to cancel previously started jobs to ensure that this does not occur
Currently, the lint, validate and convert action runs when a commit is made into a PR. If two commits are made in close sequence then two actions can be launched, when only the latter needs to complete.
This can cause the second action to fail in the commit phase of the conversion job as it seems that there are unstashed changes from when the first job overwrote the JSON-LD.
We can use GitHub actions concurrency to cancel previously started jobs to ensure that this does not occur
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#concurrency
The text was updated successfully, but these errors were encountered: