git-nested 1.0.3__tar.gz

git_nested-1.0.3/.codecov.yml

@@ -0,0 +1,18 @@
+# CodeCov config for Pull-Request comments
+
+comment:
+  layout: "reach, diff, flags, files"
+  behavior: default
+  require_changes: false
+  require_base: false
+  require_head: true
+  hide_project_coverage: false
+
+coverage:
+  status:
+    project:
+      default:
+        informational: true
+    patch:
+      default:
+        informational: true

git_nested-1.0.3/.fish.rc

@@ -0,0 +1,17 @@
+#------------------------------------------------------------------------------
+#
+# This is the `git-nested` initialization script.
+#
+# This script turns on the `git-nested` Git subcommand for the *Fish* shell.
+#
+# Just add a line like this to your `~/.config/fish/config.fish`:
+#
+#   source /path/to/git-nested/.fish.rc
+#
+#------------------------------------------------------------------------------
+
+set GIT_NESTED_ROOT (dirname (realpath (status --current-filename)))
+set PATH $GIT_NESTED_ROOT/lib $PATH
+
+# Load git-nested completions
+source $GIT_NESTED_ROOT/share/git-nested.fish

git_nested-1.0.3/.gitattributes

@@ -0,0 +1 @@
+* text eol=lf

git_nested-1.0.3/.github/workflows/publish.yml

@@ -0,0 +1,45 @@
+name: Publish to PyPI
+
+on:
+  push:
+    tags: ['*.*.*']
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Install uv
+        uses: astral-sh/setup-uv@v7
+        with:
+          python-version: '3.13'
+          enable-cache: true
+      - name: Setup project
+        run: uv sync --frozen
+      - name: Build package
+        run: uv run poe build
+      - name: Upload dist
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/project/git-nested/
+    permissions:
+      id-token: write
+    steps:
+      - name: Download dist
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

git_nested-1.0.3/.github/workflows/test.yml

@@ -0,0 +1,45 @@
+name: Run Tests
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: ['*']
+
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        python-version: ['3.10', '3.11', '3.12', '3.13', '3.14']
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v7
+        with:
+          python-version: ${{ matrix.python-version }}
+          enable-cache: true
+      - name: Setup project
+        run: uv sync --frozen
+      - name: git config
+        run: |
+          git config --global user.email "you@example.com";
+          git config --global user.name "Your Name";
+          git config --global init.defaultBranch "master";
+          git config --global --add safe.directory "$PWD";
+          git config --global --add safe.directory "$PWD.git";
+      - name: Run poe all
+        run: uv run poe all
+      - name: Upload coverage reports to Codecov
+        if: matrix.os == 'ubuntu-latest' && matrix.python-version == '3.14'
+        uses: codecov/codecov-action@v5
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}
+      - name: Upload test results to Codecov
+        if: ${{ !cancelled() }}
+        uses: codecov/test-results-action@v1
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}

git_nested-1.0.3/.gitignore

@@ -0,0 +1,13 @@
+/test/tmp/
+__pycache__
+.venv/
+*.pyc
+*.pyo
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+.coverage
+htmlcov/
+*.whl
+*.tar.gz

git_nested-1.0.3/.rc

@@ -0,0 +1,19 @@
+#!/bin/bash
+
+[[ -n ${ZSH_VERSION-} ]] &&
+  GIT_NESTED_ROOT=$0 ||
+  GIT_NESTED_ROOT=$BASH_SOURCE
+
+[[ $GIT_NESTED_ROOT =~ ^/ ]] ||
+  GIT_NESTED_ROOT=$PWD/$GIT_NESTED_ROOT
+
+GIT_NESTED_ROOT=$(
+  cd "$(dirname "$GIT_NESTED_ROOT")" || return
+  pwd
+) || return
+
+export GIT_NESTED_ROOT
+export PATH=$GIT_NESTED_ROOT/lib:$PATH
+export MANPATH=$GIT_NESTED_ROOT/man:$MANPATH
+
+source "$GIT_NESTED_ROOT/share/enable-completion.sh"

git_nested-1.0.3/CONTRIBUTING.md

@@ -0,0 +1,187 @@
+# Contributing to git-nested
+
+Thank you for your interest in contributing to git-nested! This document provides guidelines and instructions for contributing to the project.
+
+## Code of Conduct
+
+Please be respectful and constructive in all interactions with the community. We aim to maintain a welcoming and inclusive environment for all contributors.
+
+## Getting Started
+
+### Setting Up Your Development Environment
+
+1. Fork the repository on GitHub
+2. Clone your fork locally:
+   ```bash
+   git clone https://github.com/YOUR_USERNAME/git-nested
+   cd git-nested
+   ```
+
+3. Install development dependencies:
+   ```bash
+   # Using uv (recommended)
+   uv sync --dev
+
+   # Or using pip
+   pip install -e ".[dev]"
+   ```
+
+4. Verify your setup:
+   ```bash
+   uv run poe all
+   ```
+
+## Development Workflow
+
+### Making Changes
+
+1. Create a feature branch from `main`:
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+
+2. Make your changes, following the coding standards below
+
+3. Add or update tests to cover your changes
+
+4. Run all checks before committing:
+   ```bash
+   uv run poe all
+   ```
+
+### Running Tests Individually
+
+```bash
+# Run all tests
+uv run poe test
+
+# Run specific test file
+uv run poe test test/test_clone.py
+
+# Run with verbose output
+uv run poe test -vv
+
+# You can also run pytest directly
+uv run pytest
+```
+
+### Code Quality
+
+We use [Ruff](https://github.com/astral-sh/ruff) for both linting and formatting:
+
+```bash
+# Check code quality
+uv run poe lint
+
+# Auto-format code
+uv run poe format
+```
+
+Make sure all checks pass before submitting your PR.
+
+## Coding Standards
+
+- Follow [PEP 8](https://pep8.org/) style guidelines (enforced by Ruff)
+- Write clear, descriptive commit messages
+- Add docstrings to all public functions and classes
+- Keep functions focused and single-purpose
+- Use type hints where appropriate
+- Write self-documenting code with meaningful variable names
+
+## Testing Guidelines
+
+- Write tests for all new features and bug fixes
+- Ensure existing tests still pass
+- Aim for high test coverage on modified code
+- Use descriptive test names that explain what is being tested
+- Group related tests in the same test file
+
+## Commit Message Guidelines
+
+Write clear and descriptive commit messages:
+
+- Use the imperative mood ("Add feature" not "Added feature")
+- Keep the first line under 72 characters
+- Reference issues and PRs where relevant
+- Provide additional context in the body if needed
+
+Example:
+```
+Add support for shallow clones with --depth option
+
+Implements shallow clone functionality to reduce clone time
+and disk space for large repositories.
+
+Fixes #123
+```
+
+## Submitting a Pull Request
+
+1. Push your changes to your fork:
+   ```bash
+   git push origin feature/your-feature-name
+   ```
+
+2. Open a Pull Request on GitHub against the `main` branch
+
+3. Fill out the PR template with:
+   - Clear description of the changes
+   - Motivation and context
+   - How the changes have been tested
+   - Any breaking changes or migration notes
+   - Related issue numbers
+
+4. Wait for review and address any feedback
+
+5. Once approved, a maintainer will merge your PR
+
+## Pull Request Review Process
+
+- All PRs require at least one review before merging
+- CI checks must pass (tests, linting, formatting)
+- Reviewers may request changes or clarifications
+- Be responsive to feedback and questions
+- Maintainers will merge once all requirements are met
+
+## Reporting Bugs
+
+If you find a bug, please open an issue on GitHub with:
+
+- Clear, descriptive title
+- Steps to reproduce the issue
+- Expected behavior vs actual behavior
+- Your environment (OS, Python version, git version)
+- Any relevant error messages or logs
+- Minimal reproduction example if possible
+
+## Requesting Features
+
+Feature requests are welcome! Please:
+
+- Check existing issues to avoid duplicates
+- Clearly describe the feature and its use case
+- Explain why it would be useful to other users
+- Consider submitting a PR if you can implement it
+
+## Documentation
+
+- Update documentation for any user-facing changes
+- Add docstrings to new functions and classes
+- Update README.md if adding new commands or features
+- Include code examples where helpful
+
+## Questions?
+
+- Check existing documentation and issues first
+- Open a GitHub issue for questions about contributing
+- Be patient and respectful when asking for help
+
+## License
+
+By contributing to git-nested, you agree that your contributions will be licensed under the MIT License.
+
+## Recognition
+
+Contributors will be recognized in the project. Significant contributors may be added to the AUTHORS or CONTRIBUTORS file.
+
+Thank you for contributing to git-nested!

git_nested-1.0.3/LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright 2026 - Thorsten Klein <thorsten.klein.git@gmail.com>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.