jekyll-github-metadata: add collection-valued fields
Open
Nobody has claimed this yet.
github-pages
plugins
- Dominant language
- Go
- Stars
- 394
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Implement the collection-valued fields missing from the jekyll-github-metadata emulation.
Scope
contributorspublic_repositoriesreleasesversions- pagination behavior for repositories with more than one API page
- authenticated/rate-limit error behavior that preserves the existing non-fatal plugin contract
- caching consistent with the repository metadata cache
- fixture or local HTTP-server tests; tests must not depend on live GitHub responses
Document any deliberate compatibility limits if current Ruby plugin values cannot be reproduced from the public API.
Split from #28.
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 by locating the jekyll-github-metadata emulation and the existing repository metadata cache. Use fixtures or a local HTTP server to test collection fields, pagination, authentication and rate-limit failures without live GitHub responses. Done means all listed fields, caching and non-fatal error behavior are covered, with compatibility limits documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go, jekyll
- Domain
- api, backend, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100