How jetpackduba/gitnuro works
Purpose and runtime
Gitnuro is a FOSS, native multiplatform desktop Git client built with Kotlin, Jetpack Compose Desktop, and JGit—not a web application. Gradle defines a modular JVM application; the desktop entry point is app/src/main/kotlin/com/jetpackduba/gitnuro/main.kt, which initializes application composition in app/src/main/kotlin/com/jetpackduba/gitnuro/App.kt.
Module boundaries
The repository follows layered modules:
• app: Compose UI, view models, app composition, and dependency wiring.
• domain: Git-operation contracts, use cases, domain models, state management, and service abstractions.
• data: JGit-backed implementations, persistence, networking, credential handling, and in-memory repositories.
• common: cross-module platform/coroutine utilities.
Core boundaries are visible in domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/interfaces/, domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/usecases/, and data/src/main/kotlin/com/jetpackduba/gitnuro/data/git/.
Application, tabs, and DI scopes
The app supports multiple repository tabs. Global and per-tab object graphs are separated through DI components: app/src/main/kotlin/com/jetpackduba/gitnuro/di/AppComponent.kt, app/src/main/kotlin/com/jetpackduba/gitnuro/di/TabComponent.kt, and app/src/main/kotlin/com/jetpackduba/gitnuro/TabViewModel.kt. A tab owns repository state and coroutine lifetime, isolating concurrent repository operations; common/src/main/kotlin/com/jetpackduba/gitnuro/common/TabScope.kt and domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/TabCoroutineScope.kt support that lifecycle.
UI state and interaction flow
Compose screens render state from app/repository view models and invoke domain use cases rather than data implementations directly. The top-level UI/tab composition resides in app/src/main/kotlin/com/jetpackduba/gitnuro/ui/AppTab.kt and app/src/main/kotlin/com/jetpackduba/gitnuro/ui/AppViewModel.kt; open-repository orchestration is concentrated in app/src/main/kotlin/com/jetpackduba/gitnuro/repositoryopen/RepositoryOpenViewModel.kt. Status, history/log, commit, diff, rebase, and dialogs are presentation stages that translate user actions into operations and surface loading/errors/notifications.
Domain orchestration and repository state
Domain use cases coordinate validation, action sequencing, refreshes, and error boundaries. Representative flows include repository open/refresh (domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/usecases/OpenRepositoryUseCase.kt, domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/usecases/RefreshDataUseCase.kt), workspace commit/staging (domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/usecases/DoCommitUseCase.kt), and history generation (domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/usecases/GetLogUseCase.kt). Shared state is modeled through repository contracts and domain models, notably domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/repositories/RepositoryStateRepository.kt and domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/models/RepositoryState.kt.
Git engine, filesystem, and refresh loop
The data layer executes Git operations through JGit and maps JGit objects into domain models. data/src/main/kotlin/com/jetpackduba/gitnuro/data/git/JGit.kt is the integration anchor; concrete action families cover workspace status/staging, graph/log traversal, branches, remotes, rebase, stashes, tags, and submodules. File-system changes are monitored by data/src/main/kotlin/com/jetpackduba/gitnuro/data/git/FileChangesWatcher.kt; watcher events feed the domain refresh path so the UI reflects external Git or working-tree changes.
Remote services, credentials, and LFS
Network Git operations use JGit transport plus HTTP/SSH credentials and optional external Git Credential Manager integration. Key boundaries are data/src/main/kotlin/com/jetpackduba/gitnuro/data/git/credentials/HttpCredentialsProvider.kt, data/src/main/kotlin/com/jetpackduba/gitnuro/data/git/credentials/SshCredentialsProvider.kt, and domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/credentials/external/IGitCredentialsManagerProvider.kt. Git LFS is a separate network pipeline for authentication and object upload/download, represented by data/src/main/kotlin/com/jetpackduba/gitnuro/data/repositories/NetworkLfsRepository.kt and data/src/main/kotlin/com/jetpackduba/gitnuro/data/git/lfs/.
Persistence and native/platform integration
Application settings are persisted behind the domain settings contract in domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/repositories/AppSettingsRepository.kt, implemented via data/src/main/kotlin/com/jetpackduba/gitnuro/data/UserSettingsDataStore.kt. Platform integrations cover file picking, browser/file opening, shell terminals, proxies, and OS-specific credential-manager execution. Rust/UniFFI material under rs/src/lib.rs and rs/uniffi.toml, plus native-image metadata at app/src/main/resources/META-INF/native-image/gitnuro/reachability-metadata.json, indicate native interop/packaging support alongside the JVM desktop runtime.
Main entry points: App.kt Application composition · TabViewModel.kt Repository tab state · TabComponent.kt Tab DI scope · JGit.kt JGit Git engine
Components 18
Desktop application
- Desktop entry point
app/src/main/kotlin/com/jetpackduba/gitnuro/main.kt - Application composition
app/src/main/kotlin/com/jetpackduba/gitnuro/App.kt - App DI scope · Owns global application dependencies.
app/src/main/kotlin/com/jetpackduba/gitnuro/di/AppComponent.kt - Tab DI scope · Creates isolated object graphs per repository tab.
app/src/main/kotlin/com/jetpackduba/gitnuro/di/TabComponent.kt - Repository tab state · Owns a tab's repository state and operation lifetime.
app/src/main/kotlin/com/jetpackduba/gitnuro/TabViewModel.kt - Tab UI and screens · Renders repository state and dispatches user actions.
app/src/main/kotlin/com/jetpackduba/gitnuro/ui/AppTab.kt - Open repository flow
app/src/main/kotlin/com/jetpackduba/gitnuro/repositoryopen/RepositoryOpenViewModel.kt
Domain layer
- Git service contracts · Abstractions consumed by use cases instead of data implementations.
- Git operation use cases · Validates, sequences operations, refreshes state, and handles errors.
- Repository state · Shared domain state exposed to the presentation layer.
domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/repositories/RepositoryStateRepository.kt - Tab coroutine lifetime
domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/TabCoroutineScope.kt - Settings contract
domain/src/main/kotlin/com/jetpackduba/gitnuro/domain/repositories/AppSettingsRepository.kt
Data and integrations
- JGit Git engine · Executes Git actions and maps JGit objects into domain models.
data/src/main/kotlin/com/jetpackduba/gitnuro/data/git/JGit.kt - Working-tree watcher
data/src/main/kotlin/com/jetpackduba/gitnuro/data/git/FileChangesWatcher.kt - HTTP and SSH credentials · Supplies credentials to JGit remote transport.
data/src/main/kotlin/com/jetpackduba/gitnuro/data/git/credentials/HttpCredentialsProvider.kt - Git LFS pipeline · Authenticates and transfers LFS objects separately from Git transport.
data/src/main/kotlin/com/jetpackduba/gitnuro/data/repositories/NetworkLfsRepository.kt - User settings store
data/src/main/kotlin/com/jetpackduba/gitnuro/data/UserSettingsDataStore.kt - Native interop and packaging · Supports native integration alongside the JVM desktop runtime.
rs/src/lib.rs
Connections 18
- Desktop entry point → Application composition: starts
- Application composition → App DI scope: initializes
- App DI scope → Tab DI scope: creates per tab
- Tab DI scope → Repository tab state: provides
- Tab DI scope → Tab coroutine lifetime: binds lifetime
- Application composition → Tab UI and screens: hosts
- Tab UI and screens → Repository tab state: renders and invokes
- Open repository flow → Git operation use cases: opens repository
- Repository tab state → Git operation use cases: invokes
- Repository tab state → Repository state: observes
- Git operation use cases → Git service contracts: depends on
- Git operation use cases → Repository state: updates on refresh
- Git service contracts → JGit Git engine: implemented by
- Working-tree watcher → Git operation use cases: triggers refresh
- JGit Git engine → HTTP and SSH credentials: uses for remote transport
- JGit Git engine → Git LFS pipeline: coordinates LFS transfers
- Settings contract → User settings store: implemented by
- Application composition → Native interop and packaging: packages with