chore(repo): flisk-sh/analytics has no Website URL in the About box, although the README links to analytics.flisk.si
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github, javascript
- Domain
- tooling
Research direction
The Website field is repository metadata, not a file, so start by confirming the current value with gh api repos/flisk-sh/analytics --jq .homepage and then setting it via gh repo edit. The second half needs the org hygiene script, which the issue does not name; search the repo for the existing checks that query repositories through gh api and add a failing case for a repo with a live site and empty homepage. Done when the API returns https://analytics.flisk.si, the new check fails on an empty homepage, and the existing checks still pass.
Written by the indexing model from the issue text.
Description
Problem
The GitHub repository flisk-sh/analytics has an empty "Website" field, although the README links to the live site https://analytics.flisk.si. The repository sidebar shows no link, so a visitor who finds the repo cannot get to the running product in one click, and search engines get no homepage signal.
Reproduce:
- Open the repository page on GitHub.
- Look at the About box: no website link.
- Run
gh api repos/flisk-sh/analytics --jq .homepage: the value is empty.
Expected: the Website field is set to https://analytics.flisk.si.
Root Cause Analysis
The repository was created and deployed without filling in the About box. The homepage is repository metadata, not a file, so no check or review catches it.
TDD Fix Plan
- RED: Add a check to the org hygiene script that fails when a repository with a live site has an empty homepage.
GREEN: Set the Website field withgh repo edit flisk-sh/analytics --homepage https://analytics.flisk.si.
REFACTOR: Run the same check across all org repositories so new ones are caught.
Acceptance Criteria
- The Website field shows https://analytics.flisk.si
-
gh api repos/flisk-sh/analytics --jq .homepagereturns it - The hygiene check fails when the field is empty
- Existing checks still pass
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- Avg merge
- 1h 33m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from flisk-sh/analytics
-
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
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
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
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
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
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
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
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
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
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
All issues in flisk-sh/analytics
Similar issues
-
chore cloudflare-workers consistency d1 difficulty: easy documentation dx enhancement good first issue help wanted hygiene javascript maintenance priority: P3 seo
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MattiaPARRINELLO/backstage#70 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
untemps/svelte-palette#298 ·