Skip to content

Git Integration

Kisuke provides complete Git functionality optimized for mobile devices. View changes, make commits, manage branches, and synchronize with remote repositories through an intuitive visual interface.

  • Visual diff viewer for easy change review
  • Branch management with merge and rebase support
  • Commit history with search and filtering
  • Remote synchronization (push, pull, fetch)
  • Conflict resolution tools
  • Stash management for work in progress
  • Workspace tabs for multiple repositories
  1. Tap the Git tab in the bottom navigation
  2. Select an existing workspace or create new
  3. View repository status and recent commits

Workspaces represent different Git repositories:

  • Each tab maintains independent repository state
  • Switch between projects without losing context
  • Automatic detection of Git repositories
  • Visual status indicators for quick reference

The changes view displays all modifications in your working directory:

StatusColorDescription
ModifiedYellowExisting files with changes
AddedGreenNew files not yet tracked
DeletedRedFiles removed from repository
RenamedBlueFiles moved or renamed

Select files to include in your commit:

  • Tap individual files to stage/unstage
  • Use “Stage All” for bulk operations
  • Review staged changes before committing

Create meaningful commit messages:

  1. Enter a concise summary (50 characters or less)
  2. Add detailed description if needed
  3. Review staged files
  4. Tap Commit to save changes
  • Switch branches - Tap current branch name to see all branches
  • Create branch - Start new features or fixes
  • Delete branch - Remove merged or obsolete branches
  • Track remote - Link local branches to remote counterparts

Combine branch changes:

  • Merge preserves complete history
  • Rebase creates linear history
  • Visual conflict resolution when needed

Keep your repository synchronized:

  1. Pull - Fetch and merge remote changes
  2. Push - Upload local commits to remote
  3. Fetch - Update remote information without merging

When changes conflict:

  1. Kisuke highlights conflicting files
  2. Open conflict resolver
  3. Choose desired changes or edit manually
  4. Mark as resolved and commit

Save work temporarily without committing:

  • Stash uncommitted changes
  • Apply stashes later
  • Manage multiple stashes
  • Include untracked files optionally

Navigate repository history:

  • Browse commit list chronologically
  • View commit details and diffs
  • Search by message, author, or date
  • Cherry-pick specific commits

Rewrite history safely:

  • Reorder commits
  • Squash related changes
  • Edit commit messages
  • Split large commits

Quick repository status:

  • Clean (✓) - No uncommitted changes
  • Modified (n) - Number of changed files
  • Behind (↓n) - Commits available to pull
  • Ahead (↑n) - Commits ready to push

Visual cues in file lists:

  • Git status icons
  • Change indicators
  • Conflict markers
  • Staging state

Configure Git identity:

git config user.name "Your Name"
git config user.email "[email protected]"

Customize behavior:

  • Default branch name
  • Merge strategy
  • Auto-fetch intervals
  • Diff display preferences
  • Make atomic commits (one logical change)
  • Write clear, descriptive messages
  • Reference issue numbers when applicable
  • Review changes before committing
  • Use descriptive branch names
  • Keep branches focused on single features
  • Delete branches after merging
  • Regularly sync with remote
  • Commit frequently to avoid data loss
  • Use visual tools over command line
  • Leverage touch gestures for navigation
  • Enable auto-save in editor

Detached HEAD state

  • Create new branch from current position
  • Or checkout existing branch

Push rejected

  • Pull latest changes first
  • Resolve any conflicts
  • Push again after merging

Large repository performance

  • Limit history depth in settings
  • Use shallow clones when possible
  • Enable background fetch