Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feat] Use GH Actions to compile a repo summary that can be downloaded directly through GH pages #493

Open
chrisguida opened this issue Feb 9, 2024 · 4 comments
Assignees

Comments

@chrisguida
Copy link
Collaborator

from @cdecker: Any chance we can use GH Actions to compile a repo summary that can be downloaded directly through GH pages (saves the SSH connection overhead, and does not need a full (recursive) clone)? That'd be perfect to keep the repo metadata sync minimal and quick. (see the sparse crates.io metadata refresh deployed in 1.71 as an example of what the advantages could be).

cc @endothermicdev

@sip-21 sip-21 self-assigned this Mar 21, 2024
@chrisguida
Copy link
Collaborator Author

I imagine this would be fairly easy to implement with the badges branch @sip-21 added to deploy the CI badges.

What format do we want the metadata to be in?

cc @endothermicdev Guessing this is for reckless?

@endothermicdev
Copy link
Contributor

This wasn't intended for reckless, but it could be useful if we had it.

@chrisguida
Copy link
Collaborator Author

@endothermicdev thanks! Can you provide a bit more detail as to what this would be useful for, what the design would look like and/or how to test it? I can probably make something but I need more detail.

@endothermicdev
Copy link
Contributor

This could be useful when looking to update a plugin. Reckless could fetch this data and skip fetching the whole repository if there's no update to a plugin we care about. A last-modified date and either a checksum or the last commit affecting each plugin would be useful here. The benefit is that the github api request limit is rather low if you're not authenticated, so this could be lighter weight / quicker than fetching the whole repo on each check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants