How romboooo/release-radar works
release-radar is a terminal-based GitHub release tracker with both command-line and interactive TUI workflows. The executable opens a local SQLite database and creates a tracker service, then selects the CLI when arguments are supplied or the TUI otherwise. Users can add, list, check, review history, and delete tracked repositories. Checks prefer GitHub releases, fall back to the latest stable semantic-version tag when no release exists, and persist discoveries. The excerpts show these principal calls; the GitHub client also exposes tag and repository-existence requests.
Main entry points: main.go Application startup · tracker.go Tracker service · tui.go Interactive TUI · cli.go CLI commands
Components 8
Application entry
- Application startup
cmd/rradar/main.go
User interfaces
- CLI commands
internal/cli/cli.go - Interactive TUI
internal/tui/tui.go
Tracking domain
- Tracker service
internal/tracker/tracker.go - GitHub API client
internal/github/client.go
Persistence
- SQLite store
internal/store/sqlite.go
Other components
- Terminal user
- GitHub API
Connections 11
- Terminal user → Application startup: runs commands
README.md - Application startup → SQLite store: opens database
cmd/rradar/main.go - Application startup → Tracker service: creates service
cmd/rradar/main.go - Application startup → CLI commands: dispatches arguments
cmd/rradar/main.go - Application startup → Interactive TUI: runs interactive mode
cmd/rradar/main.go - Terminal user → Interactive TUI: uses TUI
README.md - CLI commands → Tracker service: invokes commands
internal/cli/cli.go - Interactive TUI → Tracker service: invokes actions
internal/tui/tui.go - Tracker service → SQLite store: reads and writes
internal/tracker/tracker.go - Tracker service → GitHub API client: checks repositories
internal/tracker/tracker.go - GitHub API client → GitHub API: requests repository data
internal/github/client.go