tursodatabase / tursodatabase/libsql
Enhance extensions test github workflow
Open
Nobody has claimed this yet.
ci
good first issue
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
The workflow in question: https://github.com/tursodatabase/libsql/blob/d178de8/.github/workflows/extensions-test.yml
We can do bunch of optimisations / enhancement:
- Use cargo cache to cache the dependencies
- There are three branches of tests, all of them build libsql and then run their particular tests. We should make building the libsql as a common part and then branch out to individual tests
- Setup runner to run on mac and windows machines
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/extensions-test.yml and read how its three test branches currently build libsql. Check the workflow's dependency caching and runner configuration, then verify that the shared build and individual extension tests work on the requested macOS and Windows runners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100