Skip to content

Added Hackabile (Android hackatime client) to extensions.#1405

Open
nilanshsharma23 wants to merge 2 commits into
hackclub:mainfrom
nilanshsharma23:main
Open

Added Hackabile (Android hackatime client) to extensions.#1405
nilanshsharma23 wants to merge 2 commits into
hackclub:mainfrom
nilanshsharma23:main

Conversation

@nilanshsharma23

Copy link
Copy Markdown

Summary of the problem

There wasn't a mobile client for hackatime before. So I decided to make one.

Describe your changes

I added the link and the source of this mobile client to the extensions page.

Screenshots / Media

image

@greptile-apps

greptile-apps Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds a new community extension entry — "Hackabile," an Android client for Hackatime — to the Extensions page data array in Index.svelte. No logic, routing, or backend code is changed.

  • The new entry follows the existing EXTENSIONS array structure correctly, and the source and description fields look fine.
  • The install URL is pinned to a specific release tag (/releases/tag/v1.0) rather than the general /releases page used by every other extension; this will silently serve stale installation links once newer versions are published.

Confidence Score: 4/5

Safe to merge with a minor fix to the install URL before it becomes stale.

The change is a one-entry addition to a static data array with no backend, routing, or security implications. The only issue is the install link pointing to a pinned release tag rather than the general releases page, meaning future Android releases won't be surfaced to users who click Install.

app/javascript/pages/Extensions/Index.svelte — specifically the install URL for the new Hackabile entry.

Important Files Changed

Filename Overview
app/javascript/pages/Extensions/Index.svelte Adds the Hackabile Android client entry to the EXTENSIONS array; install URL is pinned to the v1.0 tag rather than the general releases page, which will become stale as new versions ship.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Extensions Page loads] --> B[Renders EXTENSIONS array]
    B --> C[Each extension card]
    C --> D[Install button]
    C --> E[Source button]
    D --> F["Hackatime Desktop: /releases"]
    D --> G["Cattatime: /releases/"]
    D --> H["Hackabile NEW: /releases/tag/v1.0 - pinned"]
    E --> I["github.com/nilanshsharma23/hackabile"]
Loading
Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
app/javascript/pages/Extensions/Index.svelte:36
The `install` URL is pinned to the `v1.0` tag. When newer versions are released, users will be directed to the old v1.0 release instead of the latest one. Every other extension (Hackatime Desktop, Cattatime) links to the general `/releases` page so users always land on the newest release.

```suggestion
      install: "https://github.com/nilanshsharma23/hackabile/releases",
```

Reviews (1): Last reviewed commit: "Merge branch 'hackclub:main' into main" | Re-trigger Greptile

name: "Hackabile",
source: "https://github.com/nilanshsharma23/hackabile",
description: "Android app for Hackatime.",
install: "https://github.com/nilanshsharma23/hackabile/releases/tag/v1.0",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 The install URL is pinned to the v1.0 tag. When newer versions are released, users will be directed to the old v1.0 release instead of the latest one. Every other extension (Hackatime Desktop, Cattatime) links to the general /releases page so users always land on the newest release.

Suggested change
install: "https://github.com/nilanshsharma23/hackabile/releases/tag/v1.0",
install: "https://github.com/nilanshsharma23/hackabile/releases",
Prompt To Fix With AI
This is a comment left during a code review.
Path: app/javascript/pages/Extensions/Index.svelte
Line: 36

Comment:
The `install` URL is pinned to the `v1.0` tag. When newer versions are released, users will be directed to the old v1.0 release instead of the latest one. Every other extension (Hackatime Desktop, Cattatime) links to the general `/releases` page so users always land on the newest release.

```suggestion
      install: "https://github.com/nilanshsharma23/hackabile/releases",
```

How can I resolve this? If you propose a fix, please make it concise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant