NIGHT BANDIT: How To

Set up one selected text file for reviewed GitHub synchronization on Windows.

Early source release

Version 0.3.1 is an early Windows source release. General-public GitHub App authorization is not yet verified. New users may be unable to connect repositories. If GitHub denies access, stop and contact Frontline; do not bypass permissions or use someone else's credentials.

View NIGHT BANDIT on GitHub

Before you start

  • Windows 10/11, Python with Tkinter, and Git for Windows on PATH. Python 3.15 was tested; other versions have not been certified.
  • An existing GitHub repository and local checkout, with one already tracked, nonempty UTF-8 text file up to 8 MiB.
  • Your Git author name and email configured, plus suitable repository access through the GitHub App.
  • Use a dedicated application folder separate from the repository you will monitor. This release does not clone or initialize monitored repositories.
  • Code and Frontline branding are all rights reserved. Third-party fonts retain their own licenses. No subscription is required.

Download and open

  1. Step 1: Open the public GitHub repository and read its README, LICENSE and latest release notes before downloading.

  2. Step 2: In your chosen application folder's parent, run: git clone https://github.com/kjohnsonthecoder/Night-Bandit.git

  3. Step 3: Run: cd Night-Bandit

  4. Step 4: Open the application with: pythonw -B run-night-bandit.pyw. For startup diagnostics use python -B run-night-bandit.pyw.

Connect one repository

  1. Step 1: Choose Add Repository, then GitHub. Follow device authorization. No Client ID or secret entry is required. GitLab and Bitbucket are Coming Soon.

  2. Step 2: Select your authorized repository, its existing local checkout, and one tracked text file. Review the exact remote, branch and file.

  3. Step 3: Run safe dry-run. Resolve reported exclusions, divergence, permissions or recovery blockers before proceeding. Never remove locks or discard changes to make it pass.

  4. Step 4: Choose Start Automatic Sync and approve the displayed scope for this session. Existing unsynchronized edits are included. One automatic session runs at a time.

  5. Step 5: Save a harmless change in the selected file and check the activity result and GitHub commit. Success is reported after remote verification. Confirm only the intended file was included.

Pause or close

  • Stop ends the session after the current operation. Stop before switching execution scopes.
  • Closing an active window keeps the listener running in the Windows tray. Exit stops it.
  • Opening NIGHT BANDIT does not start synchronization. It installs no Windows startup task or service.
  • History reflects commits reachable from the local branch; the calendar does not fetch remote-only history.

Check for updates

  1. Step 1: In Settings choose Check for updates. It checks the latest stable GitHub Release anonymously; it downloads and installs nothing.

  2. Step 2: Read the release notes. Stop and Exit every NIGHT BANDIT instance before updating.

  3. Step 3: In the APPLICATION checkout, check git remote get-url origin, git branch --show-current and git status --short. Continue only if origin is the official public repository, the branch is main and the working tree is clean.

  4. Step 4: Run git pull --ff-only origin main only in that application checkout. If Git refuses, stop and review; never force or reset. Never run this update command in a monitored repository.

  5. Step 5: Reopen with pythonw -B run-night-bandit.pyw, run a safe dry-run and explicitly authorize the next session.

Troubleshooting and privacy

  • If authorization fails, public App onboarding may still be unavailable. Stop and contact the maintainer.
  • For a startup error, launch with python -B run-night-bandit.pyw to see diagnostics. Review any output before sharing it.
  • Divergence, foreign locks and unexpected changes deliberately block synchronization. Resolve the cause through reviewed recovery.
  • Do not share credentials, local profiles, audit logs, private repository details or file contents without reviewing them.
  • Preferences and protected authentication state live under your local application data, outside the application checkout. Keep that state private.
Contact Frontline