Skip to content
This repository was archived by the owner on Jan 9, 2023. It is now read-only.
This repository was archived by the owner on Jan 9, 2023. It is now read-only.

Switch to GitHub Actions? #11

Description

@klausenbusk

Hi

I'm wondering if using GitHub Actions or a similar "CI" solutions was ever considered?

Doing a regular clone of https://github.com/cdnjs/cdnjs every X hour probably isn't feasible, but Git supports sparse-checkout and partial clone (improved greatly in 2.25.0)

$ time git clone --filter=blob:none --sparse git@github.com:cdnjs/cdnjs.git
[...]
real	1m18,731s
$ cd cdnjs
$ time git sparse-checkout add '**/package.json'
[..]
real	0m24,713s
$ find | head -n 10
.
./ajax
./ajax/libs
./ajax/libs/zxcvbn
./ajax/libs/zxcvbn/package.json
./ajax/libs/zurb-ink
./ajax/libs/zurb-ink/package.json
./ajax/libs/zumper-angular-payments
./ajax/libs/zumper-angular-payments/package.json
$ du -hs
1,1G	.

I had a quick look at the autoupdate and packages tool, and all the other files only seems to be required for SRI generation, but I think that is fixable.

Assuming it is doable, should we switch? The main argument, as I see it, is "fewer moving parts".

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions