diff options
| author | aSemy <897017+aSemy@users.noreply.github.com> | 2023-01-30 22:18:43 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-01-30 22:18:43 +0100 |
| commit | 6ddd978e44134febffc857e9cd871982b4c6d36b (patch) | |
| tree | 1d03ae0efbdf1fc586c84ad6df05d882b2895e11 /plugins/base/src/main/kotlin/transformers/documentables/DefaultDocumentableMerger.kt | |
| parent | 765fb6e0d94564cf7d8a72d787588d59bd749c6f (diff) | |
| download | dokka-6ddd978e44134febffc857e9cd871982b4c6d36b.tar.gz dokka-6ddd978e44134febffc857e9cd871982b4c6d36b.tar.bz2 dokka-6ddd978e44134febffc857e9cd871982b4c6d36b.zip | |
Add concurrency cancellation for test/build GitHub Actions (#2710)
The GitHub Actions build queue can get 'stacked up' if there are a few smaller commits in quick succession. Since the actions take some time, some small commits can cause the GHA build queue to get congested.
This adds a 'concurrency' check for GitHub actions. It means that if a newer trigger comes in (for example, if you make two commits in a row on a PR), then the first job will be cancelled, allowing for the new job to run.
This helps save energy, and for faster feedback in PRs.
Reference docs: https://docs.github.com/en/actions/using-jobs/using-concurrency#example-using-concurrency-to-cancel-any-in-progress-job-or-run
Diffstat (limited to 'plugins/base/src/main/kotlin/transformers/documentables/DefaultDocumentableMerger.kt')
0 files changed, 0 insertions, 0 deletions