quarto-dev / quarto-dev/quarto-cli
CI: minimize calls to third parties during setup/testing
Open
@cscheid is already working on this.
Since Jul 24, 2023.
epic
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
I think this is a good long-term goal, actually: minimize our dependency on third parties in CI.
We go through, at least:
- CRAN (for
renv.lockdependencies) - deno.land? (the deno standard library, though I'm not sure we do this anymore)
- pip (for our
requirements.txtinstall) - github API (for
devtools:::install("yihui/knitr"), and maybe more?) - npm (for playwright in testing, and possibly other places as well)
- AWS (for binary dependencies)
I'd like to minimize the possible sources of failure here. I think the minimum feasible set is AWS + GitHub, and I'd be super happy with that outcome. I'm not sure how practical it is for us to solve the other ones.
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.
Assessment
This issue has not been assessed yet.