chore(repo): flisk-sh/analytics has no GitHub topics, so it cannot be found in search

Open Beginner friendly
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github, github-actions, javascript

Research direction

Start by running gh repo view flisk-sh/analytics --json repositoryTopics to confirm the empty list, then add 5-10 topics (language, platform, purpose, flisk) in the repository settings. For the check, look at the existing workflows under .github/workflows/ to match the project's conventions and add a step that lists public org repositories via gh repo list flisk-sh --json name,repositoryTopics,isPrivate and fails on missing topics, keeping the required-topic list in one shared file. Done means the check fails on a topicless repo, passes here, and existing tests still pass.

Written by the indexing model from the issue text.

Description

agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests

Problem

The flisk-sh/analytics repository has no GitHub topics. Topics are how people find a repository from GitHub search and the topic pages, and how lists such as "awesome" collections and GitHub's own recommendations pick it up. A visitor who searches for a Cloudflare Workers app, an AI chat site or a local-first dev tool will never see this repository.

Reproduce:

  1. Run gh repo view flisk-sh/analytics --json repositoryTopics.
  2. It prints an empty list.

Expected: 5 to 10 topics that say what the project is, its language and its platform.

Root Cause Analysis

Topics are repository settings, not files, so they are not covered by any template or CI check. Several repositories in the organization were created without them and nothing flags the gap.

TDD Fix Plan

  1. RED: Write a small script (or workflow step) that fails when a public repository in the organization has no topics.
    GREEN: Add 5 to 10 topics to this repository (language, platform, what it does, flisk).

  2. RED: Write a check that the topics include flisk.
    GREEN: Add the shared flisk topic so the organization's repositories group together.

REFACTOR: Keep the list of required topics in one place that the org-wide check reads.

Acceptance Criteria

  • The repository has at least 5 topics
  • One topic is flisk
  • A check fails when a public repository has no topics
  • All new tests pass
  • Existing tests still pass
Dominant language
JavaScript
Stars
0
Forks
2
Avg merge
1h 33m
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flisk-sh/analytics

All issues in flisk-sh/analytics

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.