Choose what the Developer Herald follows

It needs one thing to follow#

Until you follow at least one release feed, tracked issue or Hugging Face search, its rounds wait, the title bar says "Waiting for its settings", and the top of the page says what to add and where.

Suggested feeds#

The quickest start. Reeve finds the projects on this PC and their lockfiles; the Developer Herald reads what each project depends on, and finds each package's GitHub repository:

Each repository is ranked by how many of your projects use it, then by how many of their packages come from it. The page shows the first 8, the rest folded below, each with the projects and packages behind it:

• Follow makes its releases a feed, noted with who uses it, and a round reads it at once.
• Not this one stops suggesting it.
• Look again looks now. Otherwise it looks when the page starts, and every 6 hours.

A repository you follow already, one of your own, or one you dismissed isn't suggested. Without Reeve, nothing is suggested, and the page says so.

Add the rest in Settings#

Open Settings, in the title bar. Save checks every change first, and saves nothing until all are right.

Release feeds

Each is a Repo (owner/name), with:

• Its own keywords: used instead of the global Keywords for this feed. Empty uses those.
• Quiet unless relevant: releases that match no keyword are listed quietly, not counted as news. Good for a busy project where only some releases matter to you.
• Note: why you follow it, for your own memory.

Tracked issues

Each is a Repo, an issue Number, and a Note. Its news is a change of state, new comments, or a fix: a pull request that refers to it, the commit that closed it, or a commit that mentions it. News about a tracked issue is always relevant. A release that mentions a tracked issue is relevant too.

Hugging Face

An Author (a user or an organization), and Searches among their models: each a Term, Relevant (to flag its news as relevant), and a Note. A model new to a search is news, and so is one that changed. An author with no search is never searched.

Keywords

What makes a release relevant. There are none until you add some; without any, only a tracked issue makes a release relevant.

• They match case for case: "NPU" doesn't match the "npu" in "input".
• They don't match the tail of a longer word: "QNN" matches "QNNExecutionProvider" and "win-arm64", but not "XQNN".
• A number must stand alone: "#787" isn't "#7870".

Choose words your upstreams use in their notes for what matters to you: your platform, a feature, an API you call.