git-worktree-wrapper 0.1.0__tar.gz

git_worktree_wrapper-0.1.0/.github/BRANCH_PROTECTION.md

@@ -0,0 +1,112 @@
+# Branch Protection Setup
+
+This document describes how to set up branch protection for the `main` branch using GitHub's API or web interface.
+
+## Option 1: Using GitHub Web Interface (Recommended)
+
+1. Go to your repository on GitHub
+2. Navigate to **Settings** → **Branches**
+3. Click **Add rule** or edit the existing rule for `main`
+4. Configure the following settings:
+   - **Branch name pattern**: `main`
+   - ✅ **Require a pull request before merging**
+     - ✅ Require approvals: `1` (or more)
+     - ✅ Dismiss stale pull request approvals when new commits are pushed
+   - ✅ **Require status checks to pass before merging**
+     - ✅ Require branches to be up to date before merging
+     - Select required status checks:
+       - `Test (Python 3.11) / ubuntu-latest`
+       - `Test (Python 3.11) / macos-latest`
+       - `Test (Python 3.12) / ubuntu-latest`
+       - `Test (Python 3.12) / macos-latest`
+       - `Test (Python 3.13) / ubuntu-latest`
+       - `Test (Python 3.13) / macos-latest`
+       - `Lint`
+   - ✅ **Require conversation resolution before merging**
+   - ✅ **Do not allow bypassing the above settings**
+   - ✅ **Restrict who can push to matching branches** (optional, but recommended)
+   - ✅ **Allow force pushes** (unchecked - disable force pushes)
+   - ✅ **Allow deletions** (unchecked - prevent branch deletion)
+
+## Option 2: Using GitHub CLI
+
+```bash
+# Install GitHub CLI if not already installed
+# brew install gh  # macOS
+# apt install gh   # Linux
+
+# Authenticate
+gh auth login
+
+# Set branch protection rules
+gh api repos/:owner/:repo/branches/main/protection \
+  --method PUT \
+  --field required_status_checks='{"strict":true,"contexts":["Test (Python 3.11) / ubuntu-latest","Test (Python 3.11) / macos-latest","Test (Python 3.12) / ubuntu-latest","Test (Python 3.12) / macos-latest","Test (Python 3.13) / ubuntu-latest","Test (Python 3.13) / macos-latest","Lint"]}' \
+  --field enforce_admins=true \
+  --field required_pull_request_reviews='{"required_approving_review_count":1,"dismiss_stale_reviews":true}' \
+  --field restrictions=null \
+  --field allow_force_pushes=false \
+  --field allow_deletions=false
+```
+
+Replace `:owner` and `:repo` with your GitHub username and repository name.
+
+## Option 3: Using GitHub API with curl
+
+```bash
+# Set your GitHub token
+export GITHUB_TOKEN=your_token_here
+
+# Set branch protection
+curl -X PUT \
+  -H "Accept: application/vnd.github+json" \
+  -H "Authorization: Bearer $GITHUB_TOKEN" \
+  -H "X-GitHub-Api-Version: 2022-11-28" \
+  https://api.github.com/repos/vadimvolk/git-worktree-wrapper/branches/main/protection \
+  -d '{
+    "required_status_checks": {
+      "strict": true,
+      "contexts": [
+        "Test (Python 3.11) / ubuntu-latest",
+        "Test (Python 3.11) / macos-latest",
+        "Test (Python 3.12) / ubuntu-latest",
+        "Test (Python 3.12) / macos-latest",
+        "Test (Python 3.13) / ubuntu-latest",
+        "Test (Python 3.13) / macos-latest",
+        "Lint"
+      ]
+    },
+    "enforce_admins": true,
+    "required_pull_request_reviews": {
+      "required_approving_review_count": 1,
+      "dismiss_stale_reviews": true
+    },
+    "restrictions": null,
+    "allow_force_pushes": false,
+    "allow_deletions": false
+  }'
+```
+
+## Verification
+
+After setting up branch protection, verify it works:
+
+1. Create a test branch: `git checkout -b test-branch-protection`
+2. Make a change and push: `git push origin test-branch-protection`
+3. Create a pull request to `main`
+4. Verify that:
+   - The PR cannot be merged until CI tests pass
+   - The PR requires at least one approval
+   - Force push to `main` is blocked
+
+## Notes
+
+- The CI workflow runs on all branches (push events) and on pull requests to `main`
+- After merging to `main`, the CI will run again to verify the merge
+- Status checks must pass before merging pull requests
+- **Important**: After the first CI run completes, check the actual status check names in GitHub:
+  1. Go to any pull request or commit
+  2. View the "Checks" tab
+  3. Note the exact names of the status checks (e.g., "Test (Python 3.11)", "Lint")
+  4. Update the branch protection settings with the exact check names
+- Alternatively, you can require only the job names (`test` and `lint`) if GitHub supports that, or require "any status check" to pass

git_worktree_wrapper-0.1.0/.github/scripts/setup-branch-protection.sh

@@ -0,0 +1,85 @@
+#!/bin/bash
+# Setup branch protection for main branch using GitHub CLI
+
+set -e
+
+REPO_OWNER="${GITHUB_REPOSITORY_OWNER:-vadimvolk}"
+REPO_NAME="${GITHUB_REPOSITORY_NAME:-git-worktree-wrapper}"
+BRANCH="main"
+
+echo "Setting up branch protection for ${REPO_OWNER}/${REPO_NAME}:${BRANCH}"
+
+# Check if gh CLI is installed
+if ! command -v gh &> /dev/null; then
+    echo "Error: GitHub CLI (gh) is not installed."
+    echo "Install it with: brew install gh  # macOS"
+    echo "                 apt install gh   # Linux"
+    exit 1
+fi
+
+# Check if authenticated
+if ! gh auth status &> /dev/null; then
+    echo "Error: Not authenticated with GitHub CLI."
+    echo "Run: gh auth login"
+    exit 1
+fi
+
+# Set branch protection
+echo "Configuring branch protection rules..."
+
+# Create temporary JSON file for the protection payload
+# After first CI run, update the "contexts" array with actual check names
+# Example: "contexts": ["Test (Python 3.11)", "Test (Python 3.12)", "Lint"]
+TMP_FILE=$(mktemp)
+cat > "$TMP_FILE" <<EOF
+{
+  "required_status_checks": {
+    "strict": true,
+    "contexts": []
+  },
+  "enforce_admins": true,
+  "required_pull_request_reviews": {
+    "required_approving_review_count": 1,
+    "dismiss_stale_reviews": true,
+    "require_code_owner_reviews": false,
+    "require_last_push_approval": false
+  },
+  "restrictions": null,
+  "allow_force_pushes": false,
+  "allow_deletions": false,
+  "required_linear_history": false,
+  "required_conversation_resolution": true,
+  "allow_squash_merge": true,
+  "allow_merge_commit": true,
+  "allow_rebase_merge": true
+}
+EOF
+
+gh api "repos/${REPO_OWNER}/${REPO_NAME}/branches/${BRANCH}/protection" \
+  --method PUT \
+  --input "$TMP_FILE"
+
+# Clean up
+rm "$TMP_FILE"
+
+echo "✅ Branch protection configured successfully!"
+echo ""
+echo "Branch protection rules:"
+echo "  - Require pull request reviews (1 approval, author can merge own PRs)"
+echo "  - Require conversation resolution before merging"
+echo "  - Require status checks to pass"
+echo "  - Require branches to be up to date"
+echo "  - Enforce admins"
+echo "  - Disallow force pushes"
+echo "  - Disallow deletions"
+echo ""
+echo ""
+echo "⚠️  Important: Status checks are currently set to an empty list."
+echo "   After the first CI run completes:"
+echo "   1. Go to any PR or commit and check the 'Checks' tab"
+echo "   2. Note the exact status check names (e.g., 'Test (Python 3.11)', 'Lint')"
+echo "   3. Update branch protection via GitHub web interface:"
+echo "      Settings → Branches → Edit rule for 'main'"
+echo "      → Add the status checks under 'Require status checks to pass'"
+echo ""
+echo "   Or update this script with the correct context names and run it again."

git_worktree_wrapper-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,64 @@
+name: CI
+
+on:
+  push:
+    branches:
+      - '**'  # Run on all branches
+  pull_request:
+    branches:
+      - main
+      - master
+
+jobs:
+  test:
+    name: Test (Python ${{ matrix.python-version }})
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        python-version: ['3.11', '3.12', '3.13']
+    
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          version: "latest"
+      
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      
+      - name: Install dependencies
+        run: uv sync --extra dev
+      
+      - name: Run tests
+        run: uv run pytest
+
+  lint:
+    name: Lint
+    runs-on: ubuntu-latest
+    
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          version: "latest"
+      
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.11'
+      
+      - name: Install dependencies
+        run: uv sync --extra dev
+      
+      - name: Run mypy
+        run: uv run mypy src/gww

git_worktree_wrapper-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,72 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - 'v[0-9]+.[0-9]+.[0-9]+'
+
+jobs:
+  release:
+    name: Publish release
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+      contents: write
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Verify tag and extract version
+        id: version
+        run: |
+          TAG="${GITHUB_REF_NAME}"
+          if ! [[ "$TAG" =~ ^v[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
+            echo "::error::Tag '${TAG}' is not strict SemVer (vX.Y.Z). Pre-release tags are not supported."
+            exit 1
+          fi
+          VERSION="${TAG#v}"
+          echo "tag=${TAG}" >> "$GITHUB_OUTPUT"
+          echo "version=${VERSION}" >> "$GITHUB_OUTPUT"
+
+      - name: Verify pyproject.toml version matches tag
+        run: |
+          PYPROJECT_VERSION=$(grep -E '^version[[:space:]]*=' pyproject.toml | head -1 | sed -E 's/.*"([^"]+)".*/\1/')
+          if [ -z "$PYPROJECT_VERSION" ]; then
+            echo "::error::Could not extract version from pyproject.toml"
+            exit 1
+          fi
+          if [ "$PYPROJECT_VERSION" != "${{ steps.version.outputs.version }}" ]; then
+            echo "::error::pyproject.toml version '${PYPROJECT_VERSION}' does not match tag '${{ steps.version.outputs.version }}'"
+            exit 1
+          fi
+          echo "Version match: ${PYPROJECT_VERSION}"
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          version: "latest"
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+
+      - name: Build sdist and wheel
+        run: uv build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: ${{ steps.version.outputs.tag }}
+          name: ${{ steps.version.outputs.tag }}
+          generate_release_notes: true
+          files: |
+            dist/*.tar.gz
+            dist/*.whl

git_worktree_wrapper-0.1.0/.gitignore

@@ -0,0 +1,34 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+dist/
+build/
+
+# Virtual environments
+.venv/
+
+# Testing
+.pytest_cache/
+.coverage
+htmlcov/
+
+# Type checking
+.mypy_cache/
+
+# IDE
+.idea/
+*.swp
+*~
+
+# OS
+.DS_Store
+Thumbs.db
+Desktop.ini
+
+# Environment
+.env
+.env.*
+
+# Local notes
+TODO.md

git_worktree_wrapper-0.1.0/.opencode/skills/sync-docs-en-to-ru/SKILL.md

@@ -0,0 +1,114 @@
+---
+name: sync-docs-en-to-ru
+description: Sync English documentation (README.md) to Russian documentation (README.ru.md), preserving Russian language while updating structure and content. Use when the user asks to sync, update, or align README.ru.md with README.md (or asks to translate/retranslate docs from English to Russian).
+---
+
+# Sync English docs to Russian docs
+
+Synchronize the English documentation (`README.md`) to the Russian documentation (`README.ru.md`):
+- Preserve the Russian language in the output
+- Update structure to match the English version if it's more complete
+- Add missing sections from the English version
+- Ensure both documents have the same structure and content coverage
+- Maintain proper markdown formatting
+
+## User input
+
+The user may provide optional context in their message (for example: "sync only the Installation section", "focus on template functions", or "leave the Contributing section alone"). If they do, honor it. If they don't, perform a full sync.
+
+## Workflow
+
+### 1. Load both documentation files
+
+Read both files from the project root:
+- `README.md` (English — source of truth for structure and content)
+- `README.ru.md` (Russian — target file to update)
+
+### 2. Analyze structure
+
+Compare the structure of both files:
+- Extract all headings (H1, H2, H3, etc.) from both files
+- Identify sections present in English but missing in Russian
+- Identify sections present in Russian but missing in English
+- Note any structural differences (order, nesting, etc.)
+
+### 3. Content comparison
+
+For each section:
+- Compare content coverage (not exact text, but topics covered)
+- Identify missing information in Russian version
+- Note any differences in examples, code blocks, or explanations
+- Check if English version has updated or new content
+
+### 4. Sync `README.ru.md` to match `README.md`
+
+1. **Preserve Russian language** — All prose must remain in Russian. Do NOT paste English text directly. Instead:
+   - Use existing Russian text where it exists and matches the English meaning
+   - For new sections, translate English content to Russian
+   - For updated sections, update Russian text to match English meaning
+   - Maintain the same tone and style as the existing Russian documentation
+
+2. **Structure alignment**:
+   - Add missing sections from the English version (translated to Russian)
+   - Reorder sections if the English version has better organization
+   - Ensure heading levels match
+   - Remove sections that no longer exist in the English version
+
+3. **Content updates**:
+   - Add missing code examples, tables, or explanations (translate descriptions to Russian, keep code/examples as-is)
+   - Update existing sections if English version has more complete information
+   - Preserve all examples and code blocks (code stays in English, comments/descriptions translated)
+   - Translate any new English text to Russian
+
+4. **Language switcher** — Ensure the language switcher at the top is correct:
+   - Russian version: `[English](README.md) | **Русский**`
+   - Preserve this format
+
+5. **Preserve formatting**:
+   - Maintain emoji usage consistency
+   - Preserve code block formatting
+   - Keep table structures (translate table headers and content to Russian)
+   - Maintain list formatting
+
+6. **Translation guidelines**:
+   - Translate all descriptive text to Russian
+   - Keep code examples, commands, and technical terms in English (as they appear in Russian version)
+   - Translate table headers and descriptions
+   - Translate section headings
+   - Maintain technical accuracy in translation
+
+### 5. Validate
+
+After updating, verify:
+- All sections from English version are present in Russian
+- Structure matches between both files
+- No English descriptive text remains in Russian file (code is OK)
+- Markdown formatting is correct
+- Language switcher is present and correct
+- All new content is properly translated
+
+### 6. Report changes
+
+Provide a summary of:
+- Sections added (with Russian translations)
+- Sections updated
+- Structural changes made
+- Translation notes (if any terms needed clarification)
+- Any notes about content that couldn't be automatically synced
+
+## Operating principles
+
+- **Read-only on English file** — Never modify `README.md`
+- **Russian-first** — Always write/update content in Russian
+- **Structure preservation** — Match the English structure exactly
+- **Content completeness** — Ensure Russian version has all information from English version
+- **Formatting consistency** — Maintain consistent markdown formatting
+- **Translation quality** — Provide accurate Russian translations that maintain technical accuracy
+
+## Notes
+
+- If the English version has content that doesn't exist in Russian, translate it to Russian
+- If there are discrepancies, prefer the English version as the source of truth for structure and content
+- Preserve any Russian-specific improvements that don't exist in English version (but note them in the report)
+- Code blocks, commands, and technical identifiers should remain in English
+- Translate all user-facing text, descriptions, and explanations to Russian

git_worktree_wrapper-0.1.0/.python-version

@@ -0,0 +1 @@
+3.11