zed/.github
Kirill Bulatov 37f6a706cc
Invalidate Linux build caches more agressively (#8031)
We run Linux CI on regular GitHub Action runners, which have ~30GB of
disk space. This is nothing for Rust builds and, due to Cargo.lock
perturbations, we tend to accumulate enough artifacts to fill the disk
entirely since `restore-keys` alowed to keep the cache for different
lockfiles.

Instead, try to invalidate the cache more aggressively (which will cost
us more frequent ~30min Linux CI runs) to see how this will work in
comparison.

Release Notes:

- N/A
2024-02-19 14:16:39 -08:00
..
actions Format YAML files (#7887) 2024-02-15 22:04:57 -05:00
ISSUE_TEMPLATE Format YAML files (#7887) 2024-02-15 22:04:57 -05:00
workflows Invalidate Linux build caches more agressively (#8031) 2024-02-19 14:16:39 -08:00
pull_request_template.md Add a line instructing users to include media screenshots (#7790) 2024-02-14 15:36:56 -05:00