Collect a small watchlist
Start with repositories that support the jobs your readers care about. The GitHub API provides release and repository information; preserve source URLs and timestamps alongside any extracted text. A daily collector should distinguish a new event from a repeated fetch so the same release does not become several supposedly new stories.
Separate collection from interpretation
Store the upstream release note before generating a summary. A summary should describe the change, affected users and compatibility questions, not add capabilities that the source never claimed. Missing release notes and failed requests should produce an explicit pending state rather than an invented explanation.
Keep a review step
An editor checks the source and decides whether a change matters to the intended audience. A breaking configuration change may deserve attention even when a popular feature announcement does not. Link the original note and distinguish a documentation-based judgment from a tested result. The collected event is evidence, not an automatic endorsement.
Measure the work before expanding it
Run the pipeline against a small sample and record duplicates, missing sources and corrections. Test retry behavior, keep credentials outside the public site and respect API limits. The current website contains an editorial preview, not a live repository ingestion service. This note describes the proposed next workflow without implying it is already running.