We index only the data on the bazel registry which doesn't include the description of repositories.
Therefore though we index "aspect_rules_ts", we don't get the "About" line from the GH repo
I think in the same way I special-cased GH rules with the link-to-release-notes PR, we might be able to customize the data ingestion to add another data file aside from the git subrepo pointing into the bazel-central-registry and store bits like the description field.
If it's out of scope then it just has to go in the module catalog which certainly is proposed to be a home for lots of extra metadata.
We index only the data on the bazel registry which doesn't include the description of repositories. Therefore though we index "aspect_rules_ts", we don't get the "About" line from the GH repo
I think in the same way I special-cased GH rules with the link-to-release-notes PR, we might be able to customize the data ingestion to add another data file aside from the git subrepo pointing into the bazel-central-registry and store bits like the description field.
If it's out of scope then it just has to go in the module catalog which certainly is proposed to be a home for lots of extra metadata.