GitHub Highlights covers repositories that just became worth knowing about, for people who will actually run the code. Every post names the project, the commit history behind it and the day its numbers were true, because a star count with no date is not a fact.
Who it is for
People who will actually clone the thing: engineers, platform teams, anyone deciding what to bring into a stack. The assumption is that you can read a README yourself, so the post spends its words on what the README leaves out.
What gets published
Two projects a day, one post each, around five hundred words. A repository qualifies when something changed recently enough to explain the attention: a first stable release, a rewrite, a spike in stars, a licence change. Star count alone is not a story.
What does not get published
Awesome-lists, roadmaps, interview-prep repositories, course notes and cheat sheets. They collect stars faster than software does, and covering them is how a site about GitHub stops being about code.
How it is written
The details are on the disclosure page.
Contact
Corrections, tips and takedown requests: open an issue on the site repository, or write to the address listed there.