v2.1.1: Fix the mirror / use_fetch issue

[ezbz]

Issue Fixed in v2.1.1

This issue has been fixed in version 2.1.1. Here's what happened and how it was resolved:

Root Cause

The bug was introduced in PR #100 which added support for the --use-fetch flag. The original implementation incorrectly added the --mirror flag to git clone operations whenever --use-fetch was enabled. This caused all repositories cloned with --use-fetch to be created as bare repositories (mirrors) instead of normal repositories with a working tree.

The Fix

The fix separates the concerns of two different use cases:

1. --use-fetch flag: For users who want normal repositories (with working tree) but prefer using git fetch instead of git pull for updates. This is useful when you have local branches that no longer exist on the remote.

2. --mirror flag (new): For users who want bare mirror repositories for backup purposes. This automatically uses fetch instead of pull for updates, as mirrors should always use fetch.

Changes Made

• Removed the automatic --mirror flag from --use-fetch clone operations
• Added a new --mirror flag specifically for creating bare mirror repositories
• Updated the pull method to check both use_fetch and mirror flags (mirror implies use_fetch)
• Added comprehensive test coverage to ensure both flags work correctly together

Usage

For normal repositories with fetch updates:

gitlabber --use-fetch -t <token> -u <url> .

For bare mirror repositories (backups):

gitlabber --mirror -t <token> -u <url> .

Testing

All flag combinations have been thoroughly tested:

• ✅ --use-fetch alone: normal repo, uses fetch
• ✅ --mirror alone: bare repo, uses fetch
• ✅ Both flags: bare repo (mirror takes precedence), uses fetch
• ✅ Neither flag: normal repo, uses pull

The fix is available in v2.1.1 and has been tested to ensure backward compatibility while fixing the reported issue.

---

Note

Fixes --use-fetch creating bare repos, adds --mirror for backups, updates docs/tests, and bumps version to 2.1.1.

• CLI behavior:
  • Fix --use-fetch to create normal repos (no bare mirror cloning).
  • Add --mirror flag for bare mirror backups; implies using fetch for updates.
  • Clarify separation: --use-fetch (normal repos + fetch) vs --mirror (bare mirror + fetch).
• Docs: Update to explain differences between --use-fetch and --mirror.
• Tests: Add comprehensive coverage for flag combinations and interactions.
• Release: Bump version to 2.1.1 and update CHANGELOG.md (fixes --use-fetch creates bare repositories #158).

^{Written by Cursor Bugbot for commit 3d2d5a6. This will update automatically on new commits. Configure here.}

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: Fix code missing from version bump commit

The version was bumped to 2.1.1 and the CHANGELOG describes fixing the --use-fetch / --mirror issue, but the actual code changes are missing from this commit. The bug in gitlabber/git.py (where use_fetch incorrectly adds --mirror to clone operations) is still present, and the new --mirror CLI flag mentioned in the changelog doesn't exist. Users will see the fix documented but the bug will persist.

Additional Locations (1)

• gitlabber/__init__.py#L7-L8