GitRepositoryManager: A simple tool to manage multiple Git Repositories in one folder

Author: danielroth1

.gitignore

@@ -0,0 +1,239 @@
+
+app_data.json
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec.backup
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be added to the global gitignore or merged into this project gitignore.  For IntelliJ Platform
+#  plugin development:
+# https://github.com/JetBrains/intellij-community/blob/master/.gitignore
+.idea/
+
+# Visual Studio Code
+.vscode/
+*.code-workspace
+
+# Local History for Visual Studio Code
+.history/
+
+# Built Visual Studio Code Extensions
+*.vsix
+
+#########################
+# Project Specific Files
+#########################
+
+# Application debug logs
+manager_debug.log*
+*.log
+
+# Application data and settings (if you want to keep personal settings out of version control)
+# Uncomment the next line if app_data.json contains personal/sensitive data:
+# app_data.json
+
+# PyInstaller build artifacts
+dist/
+build/
+*.spec.backup
+
+# Application lock files
+git_repository_manager.lock
+*.lock
+
+# Windows batch file outputs
+*.bat.log
+
+# Temporary files
+temp/
+tmp/
+*.tmp
+*.temp
+
+# OS specific files
+# macOS
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db
+
+# Windows
+Thumbs.db
+ehthumbs.db
+Desktop.ini
+$RECYCLE.BIN/
+*.cab
+*.msi
+*.msm
+*.msp
+*.lnk
+
+# Linux
+*~
+
+# Backup files
+*.bak
+*.backup
+*.old
+*.orig
+*.swp
+*.swo
+
+# Runtime cache files
+.cache/
+cache/

BENCHMARKING.md

@@ -0,0 +1,129 @@
+# Benchmarking Guide
+
+## Overview
+The Git Repository Manager now includes comprehensive benchmarking capabilities to identify performance bottlenecks, especially in the `update_repository_tree_with_branch_filter` method.
+
+## Features Added
+
+### 1. Benchmark Decorator
+```python
+@benchmark
+def my_method(self):
+    # Method will be automatically timed
+    pass
+
+@benchmark(print_args=True)
+def my_method_with_args(self, arg1, arg2):
+    # Method will be timed and arguments will be shown
+    pass
+```
+
+### 2. Performance Monitoring Functions
+- `toggle_benchmarking()` - Enable/disable benchmarking globally
+- `time_operation(name)` - Context manager for timing specific operations
+
+### 3. UI Debug Menu
+Access via **Debug** menu in the application:
+- **Toggle Benchmarking** - Turn performance monitoring on/off
+- **Profile Repository Loading** - Analyze repository scanning performance
+- **Profile Branch Filtering** - Analyze branch filtering performance
+
+## Benchmarked Methods
+
+The following methods are automatically benchmarked:
+
+1. **`update_repository_tree_with_branch_filter`** - The main slow method
+2. **`_repo_has_matching_branches`** - Checks each repository for matching branches
+3. **`_build_folder_structure`** - Builds the hierarchical folder structure
+4. **`load_branches_if_needed`** - Loads branch data when needed
+5. **`load_branches`** - Performs actual Git branch loading
+
+## Console Output
+
+### Benchmark Messages
+- 🚀 `BENCHMARK: ClassName.method_name took 0.1234 seconds`
+- ❌ `BENCHMARK: ClassName.method_name failed after 0.1234 seconds`
+
+### Detailed Performance Analysis
+When `update_repository_tree_with_branch_filter` runs, you'll see:
+- 🔍 `Filtering X repositories...`
+- ⚠️ `Repo repo_name took 0.123s` (for slow repositories)
+- 📊 `Repository filtering took 0.123s, found X matching repos`
+- 🏗️ `Folder structure building took 0.123s`
+- 🌳 `Tree building took 0.123s`
+
+## Usage Examples
+
+### 1. Test Performance
+```bash
+python benchmark_test.py
+```
+
+### 2. Disable Benchmarking Programmatically
+```python
+from git_repository_manager import BENCHMARKING_ENABLED
+BENCHMARKING_ENABLED = False
+```
+
+### 3. Time Custom Operations
+```python
+from git_repository_manager import time_operation
+
+with time_operation("My custom operation"):
+    # Your code here
+    pass
+```
+
+## Performance Analysis Tips
+
+1. **Look for patterns**: Which repositories consistently take longer?
+2. **Check branch counts**: Repositories with many branches may be slower
+3. **Network repositories**: Remote repositories may have network latency
+4. **Submodules**: These add extra overhead during filtering
+
+## Expected Performance
+
+**Normal performance** (per repository):
+- Branch loading: < 50ms
+- Branch filtering: < 10ms
+
+**Concerning performance** (investigate if you see):
+- Branch loading: > 200ms
+- Branch filtering: > 100ms
+- Total filtering time: > 5 seconds for < 100 repositories
+
+## Configuration
+
+### Global Settings
+```python
+# At the top of git_repository_manager.py
+BENCHMARKING_ENABLED = True  # Change to False to disable all benchmarking
+```
+
+### Runtime Toggle
+Use the Debug menu or call `toggle_benchmarking()` to enable/disable during runtime.
+
+## Troubleshooting
+
+If you see consistently slow performance:
+
+1. **Check repository count**: Too many repositories can slow filtering
+2. **Check branch counts**: Use `git branch -a | wc -l` in slow repositories  
+3. **Check network connectivity**: Network repositories may have latency
+4. **Check Git repository health**: Run `git fsck` in problematic repositories
+5. **Check disk I/O**: SSD vs HDD can impact Git operations significantly
+
+## Sample Output
+
+```
+🚀 BENCHMARK: GitRepositoryManager.update_repository_tree_with_branch_filter took 2.1234 seconds
+🔍 Filtering 45 repositories...
+  ⚠️  Repo large-project took 0.156s
+  ⚠️  Submodule complex-submodule took 0.203s
+📊 Repository filtering took 1.234s, found 12 matching repos
+🏗️  Folder structure building took 0.456s
+🌳 Tree building took 0.789s
+🚀 BENCHMARK: GitRepositoryManager._build_folder_structure took 0.4567 seconds
+```
+
+This shows that repository filtering is the bottleneck, with two specific repositories being slow.