Updates for "Repository Explorer"

[rokubop]

• Filters:
  • Consolidate filter tags that are similar
  • Hide tags that are implicit / obvious, like "talon" or "voice"
  • Parse repo names to count toward existing tags
• Weekly CI rebuild + manual workflow trigger + show date built
• Update repo exclusion list
• Stronger safety warning with link to report suspicious repos

Before	After

[netlify]

✅ Deploy Preview for talon-wiki-refactor ready!

Name	Link
🔨 Latest commit	daeaf95
🔍 Latest deploy log	https://app.netlify.com/projects/talon-wiki-refactor/deploys/69d1f9095c248d0008ee76aa
😎 Deploy Preview	https://deploy-preview-404--talon-wiki-refactor.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Enyium]

Tag Consolidation

• garrysmod/gmod and slaythespire/slaythespire-mod can be consolidated. These are games, so quite specific, meaning more space and attention than for a single tag for each isn't warranted. They should probably be consolidated with game, since it's not useful to select a tag and have only a single repo left (if things on a certain axis are groupable at all). Tags should rather be not-too-broad groups.
• gameboyadvance and mgba are used by the same repo, refer to basically the same thing and can be consolidated. Consolidating them with game seems the best.
• blazor-server and blazor-components could also be consolidated to just blazor. They're used by the same repo, and that level of differentiation should be unnecessary.
• awesome and awesome-list should also be consolidated, because this issue is likely to be fulfilled. Probably to awesome-list, or even just list because there will probably be no other awesome list for Talon, but there may be a chance of other lists.
• I'm not sure whether it would be wise to consolidate vscode and vscode-extension. Currently, all repos with vscode are extensions. But could there be other use cases where a Talon repo is VS Code-related, but not a VS Code extension? Theoretically, the vscode tag could be hidden if the code determined that every repo that has it also has the vscode-extension tag. (I asked one repo owner to add the single missing vscode-extension tag.)

Warning Message

The warning message says "may not be curated". Isn't it that they aren't curated? Perhaps phrase it like this (also reorders sentences and corrects casing):

⚠️ Use at your own risk: This compilation wasn't reviewed. For a curated list, visit Talon user file sets. Do not download or run anything from unvetted repositories without careful review. To report a suspicious repository, please open an issue.

[rokubop]

Thanks for the feedback @Enyium updated images above with suggestions + parsed repo names to also contribute to existing tags (about 60% repos don't have tags, so this helps with that)

[Enyium]

Very nice!

Currently (with many repos untagged and - according to a rough assessment - 27 repos in awesome-talon without the talonvoice tag), the tag counts in the Explorer are rather low. But to solve cases like where someone wants to see vscode repos not being vscode-extensions (just as an example), it would be an idea to let the user exclude tags from the list. Of course, this could be implemented in various ways. But since the page is likely to be controlled using voice (and Rango), perhaps a switch would be best that toggles between being able to include and to exclude. Exclusions should obviously be highlighted with red color. You could additionally allow for the opposite when clicking tags while a modifier is held.

But if this would be implemented, the tag list should also at least slightly highlight which tags are used by the currently listed repos.