Skip to content

Add TrackFlow to the list of ActivityWatch forks - #178

Open
CODEX-cpp wants to merge 1 commit into
ActivityWatch:masterfrom
CODEX-cpp:add-trackflow-fork
Open

Add TrackFlow to the list of ActivityWatch forks#178
CODEX-cpp wants to merge 1 commit into
ActivityWatch:masterfrom
CODEX-cpp:add-trackflow-fork

Conversation

@CODEX-cpp

Copy link
Copy Markdown

Adds TrackFlow to the "Examples of forks" list in forking.rst, as requested there ("If you fork ActivityWatch, please add your fork to this list.").

TrackFlow is a Windows desktop fork rewritten in Rust/Tauri: a single in-process server with no open network port, a redesigned UI, project/stopwatch tracking, category tagging, custom notifications, and an extensible custom-watcher system for tracking arbitrary data sources.

It follows the forking requirements described on this same page: its own name and logo, no affiliation with the main ActivityWatch project, same license (MPL-2.0), public source code.

TrackFlow (https://github.com/CODEX-cpp/TrackFlow) is a Windows desktop
fork rewritten in Rust/Tauri, adding a redesigned UI, project/stopwatch
tracking, category tagging, custom notifications, and an extensible
custom-watcher system.
@greptile-apps

greptile-apps Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Adds TrackFlow to the documented examples of ActivityWatch forks.

  • Links to the TrackFlow GitHub repository using the existing Sphinx gh role.
  • Summarizes the fork’s Windows, Rust/Tauri, tracking, notification, and extensibility features.

Confidence Score: 5/5

The documentation-only change appears safe to merge.

The new entry follows the existing reStructuredText list and GitHub-role syntax, with no build, behavioral, or security failure identified.

Important Files Changed

Filename Overview
src/forking.rst Adds one convention-compliant entry to the existing list of ActivityWatch forks; no actionable issue was identified.

Reviews (1): Last reviewed commit: "Add TrackFlow to the list of ActivityWat..." | Re-trigger Greptile

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