Austin Seipp 643d772bab github: cancel in-progress builds on stale PRs ... When a pull request is pushed multiple times in sequence (e.g. to fix small errors that are noticed post-submission), a backlog of builds ends up needing to be cleared out before your new update can be built. If you push N times, N builds are queued and need to clear out first. This can cause higher latency for *every* PR since the pool of public runners is shared, and in general seems uneconomical and inefficient since 99% of the time you want to build the new version ASAP. Luckily GHA has a universal solution to this: use the `concurrency` directive to group all builds for a PR under a name, and when a new build appears in that group, cancel all builds in the group that are in-progress. Taken from this useful blog post: "Simple trick to save environment and money when using GitHub Actions" https://turso.tech/blog/simple-trick-to-save-environment-and-money-when-using-github-actions Signed-off-by: Austin Seipp <aseipp@pobox.com>		2024-11-08 09:27:42 -06:00
..
ISSUE_TEMPLATE
scripts	require poetry 1.8, recommend installing it via pipx	2024-05-27 10:53:35 -07:00
workflows	github: cancel in-progress builds on stale PRs	2024-11-08 09:27:42 -06:00
dependabot.yml
PULL_REQUEST_TEMPLATE.md	bookmarks: update some leftover uses of the word "branch"	2024-09-11 19:19:31 -07:00