Redo caching based on `Cargo.lock`

Open
#779 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, rust
Domain
build-system, ci-cd

Research direction

Start by comparing FlightCore's existing workflow caching with the referenced .github/workflows/build.yml example and inspect how Cargo.lock is used. The work is done when the cache identifier is based on the Cargo.lock checksum without the separate caching action, and the workflow still restores and updates the intended cache.

Written by the indexing model from the issue text.

Description

I started working on another Rust project and it seems like caching works a lot better there by just using the checksum of the Cargo.lock file as the identifier instead of using a separate action.

https://github.com/GeckoEidechse/mdbook-gitbook/blob/16969b1d187940029c96183e6409b1de35e6d7a9/.github/workflows/build.yml#L13-L21

Might be worth trying the same thing for FlightCore 👀

Dominant language
Rust
Stars
94
Forks
20
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from R2NorthstarTools/FlightCore

All issues in R2NorthstarTools/FlightCore

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.