commitrocket 0.1.1__tar.gz

commitrocket-0.1.1/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,65 @@
+name: Bug report
+description: Something did not work as expected
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for reporting a bug. Please check the [README](https://github.com/coldsofttech/CommitRocket#readme)
+        and existing issues first. Do not include secrets, tokens or private file names.
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: What did you expect, and what happened instead?
+    validations:
+      required: true
+  - type: textarea
+    id: command
+    attributes:
+      label: Command you ran
+      description: The full `commitrocket` command, including options.
+      render: shell
+    validations:
+      required: true
+  - type: textarea
+    id: output
+    attributes:
+      label: Output or error
+      description: Paste the terminal output. The log file path is printed at the end of every run.
+      render: text
+  - type: textarea
+    id: log
+    attributes:
+      label: Relevant log lines
+      description: Re-run with `--level DEBUG` and paste the relevant part of the log file, with any private paths removed.
+      render: text
+  - type: input
+    id: version
+    attributes:
+      label: CommitRocket version
+      description: Output of `commitrocket --version`
+    validations:
+      required: true
+  - type: dropdown
+    id: os
+    attributes:
+      label: Operating system
+      options:
+        - Windows
+        - macOS
+        - Linux
+        - Other
+    validations:
+      required: true
+  - type: input
+    id: tooling
+    attributes:
+      label: Python, Git and git-lfs versions
+      description: For example `Python 3.12, git 2.47, git-lfs 3.6`. `commitrocket doctor` shows these.
+  - type: input
+    id: host
+    attributes:
+      label: Git host
+      description: For example GitHub, GitLab, Bitbucket, self-hosted.

commitrocket-0.1.1/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Report a security vulnerability
+    url: https://github.com/coldsofttech/CommitRocket/security/advisories/new
+    about: Please report security problems privately, not in a public issue.
+  - name: Questions and ideas
+    url: https://github.com/coldsofttech/CommitRocket/discussions
+    about: Ask a question or float an idea before opening an issue.

commitrocket-0.1.1/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,30 @@
+name: Feature request
+description: Suggest an improvement or a new option
+title: "[Feature]: "
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem are you trying to solve?
+      description: Describe the situation, not only the solution.
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: What would you like to happen?
+      description: For example a new option, a change in behavior, or a new output.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives you considered
+      description: Workarounds you use today, or other designs.
+  - type: checkboxes
+    id: contribute
+    attributes:
+      label: Contributing
+      options:
+        - label: I would be willing to open a pull request for this.

commitrocket-0.1.1/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+## What does this change?
+
+<!-- A short summary, and why it is needed. Link the issue it closes, e.g. "Closes #123". -->
+
+## How was it tested?
+
+<!-- Commands you ran and anything you checked by hand. -->
+
+## Checklist
+
+- [ ] `uv run ruff check .` passes
+- [ ] `uv run pytest -m "not integration"` passes
+- [ ] `uv run pytest -m integration` passes (if the change touches the run flow, Git handling or LFS)
+- [ ] Tests added or updated for the change
+- [ ] `CHANGELOG.md` has a short entry under `[Unreleased]` (what changed for the reader, in one or two lines)
+- [ ] `README.md` updated if user-facing behavior or options changed; technical details go in `docs/`
+- [ ] No secrets, tokens or private paths in the code, tests or logs

commitrocket-0.1.1/.github/dependabot.yml

@@ -0,0 +1,33 @@
+version: 2
+
+updates:
+  # Python dependencies and the uv.lock file
+  - package-ecosystem: "uv"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    commit-message:
+      prefix: "chore(deps)"
+    groups:
+      python-dependencies:
+        patterns: ["*"]
+        update-types: ["minor", "patch"]
+
+  # Actions used in .github/workflows
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    commit-message:
+      prefix: "chore(ci)"
+    groups:
+      github-actions:
+        patterns: ["*"]
+
+  # Hook versions in .pre-commit-config.yaml
+  - package-ecosystem: "pre-commit"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    commit-message:
+      prefix: "chore(deps)"

commitrocket-0.1.1/.github/workflows/lint.yml

@@ -0,0 +1,27 @@
+name: Lint
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+concurrency:
+  group: lint-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  ruff:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: astral-sh/setup-uv@v7
+
+      - name: Install
+        run: uv sync --python 3.11
+
+      - name: Ruff
+        run: uv run ruff check .

commitrocket-0.1.1/.github/workflows/release.yml

@@ -0,0 +1,69 @@
+name: Release
+
+# Publishes to PyPI when a version tag such as v0.2.0 is pushed.
+# Needs a PYPI_API_TOKEN secret (Settings > Secrets and variables > Actions).
+on:
+  push:
+    tags: ["v*.*.*"]
+
+permissions:
+  contents: read
+
+jobs:
+  check:
+    name: Check version and tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: astral-sh/setup-uv@v7
+
+      - name: Tag must match the package version
+        shell: bash
+        run: |
+          tag="${GITHUB_REF_NAME#v}"
+          project=$(python3 -c "import tomllib; print(tomllib.load(open('pyproject.toml', 'rb'))['project']['version'])")
+          module=$(python3 -c "import re; print(re.search(r'__version__ = \"(.+?)\"', open('src/commitrocket/__init__.py').read()).group(1))")
+          echo "tag=$tag pyproject=$project __init__=$module"
+          if [ "$tag" != "$project" ] || [ "$tag" != "$module" ]; then
+            echo "::error::Tag v$tag must match the version in pyproject.toml ($project) and src/commitrocket/__init__.py ($module)."
+            exit 1
+          fi
+
+      - name: Install
+        run: uv sync --python 3.11
+
+      - name: Lint
+        run: uv run ruff check .
+
+      - name: Unit tests
+        run: uv run pytest -m "not integration"
+
+      - name: Integration tests
+        run: uv run pytest -m integration
+
+  publish:
+    name: Build and publish
+    needs: check
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: astral-sh/setup-uv@v7
+
+      - name: Build
+        run: uv build
+
+      - name: Publish to PyPI
+        env:
+          UV_PUBLISH_TOKEN: ${{ secrets.PYPI_API_TOKEN }}
+        run: uv publish
+
+      - name: GitHub release
+        uses: softprops/action-gh-release@v3
+        with:
+          generate_release_notes: true
+          files: dist/*

commitrocket-0.1.1/.github/workflows/tests.yml

@@ -0,0 +1,45 @@
+name: Tests
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+concurrency:
+  group: tests-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    name: ${{ matrix.os }} / Python ${{ matrix.python }}
+    runs-on: ${{ matrix.os }}
+    # Python 3.15 may still be a pre-release; don't let it block the build.
+    continue-on-error: ${{ matrix.python == '3.15' }}
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - { os: ubuntu-latest, python: "3.11" }
+          - { os: ubuntu-latest, python: "3.12" }
+          - { os: ubuntu-latest, python: "3.13" }
+          - { os: ubuntu-latest, python: "3.14" }
+          - { os: ubuntu-latest, python: "3.15" }
+          - { os: windows-latest, python: "3.11" }
+          - { os: macos-latest, python: "3.11" }
+
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: astral-sh/setup-uv@v7
+
+      - name: Install
+        run: uv sync --python ${{ matrix.python }}
+
+      - name: Unit tests
+        run: uv run pytest -m "not integration" -n auto
+
+      - name: Integration tests
+        run: uv run pytest -m integration -n auto

commitrocket-0.1.1/.gitignore

@@ -0,0 +1,223 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$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
+
+# 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
+*.lcov
+.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
+
+# uv
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.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
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi/*
+!.pixi/config.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
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs/Zensical 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 found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore that
+#   can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, you
+#   could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+CLAUDE.md
+.temp/

commitrocket-0.1.1/.pre-commit-config.yaml

@@ -0,0 +1,17 @@
+# Install once with: uv run pre-commit install
+# Integration tests (marker "integration") are slower and run only in CI.
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.17.2
+    hooks:
+      - id: ruff
+        args: [--fix, --exit-non-zero-on-fix]
+
+  - repo: local
+    hooks:
+      - id: pytest
+        name: pytest (unit tests)
+        entry: uv run pytest -m "not integration" -n auto -q
+        language: system
+        types: [python]
+        pass_filenames: false

commitrocket-0.1.1/.python-version

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

commitrocket-0.1.1/CHANGELOG.md

@@ -0,0 +1,48 @@
+# Changelog
+
+## [Unreleased]
+
+## [0.1.1] - 2026-10-24
+
+### Added
+- Issue and pull request templates, a security policy, a code of conduct and contributing guidelines.
+- Dependabot keeps dependencies, GitHub Actions and pre-commit hooks up to date.
+
+### Fixed
+- Batches with thousands of files no longer fail on Windows with "The filename or extension is too long".
+
+### Security
+- A config file found inside a repository can no longer turn on `force`, set the remote or branch, write reports or logs, or read pattern files; use `--config` for those.
+- File names with characters like `[` or `*` are treated literally, so they no longer pull other files into a batch.
+- `--remote` and `--branch` values that look like Git options are rejected.
+- Credentials inside remote URLs are hidden in logs, errors and reports, and log and report files are readable only by you.
+- File names with line breaks are refused when creating LFS rules.
+- Square brackets in file names and Git messages no longer break or hide output.
+
+## [0.1.0] - 2026-10-24
+
+### Added
+- CommitRocket is now an installable package with a `commitrocket` command.
+- Files over 100 MiB are detected up front, and the run stops with a hint to use `--use-lfs` instead of failing at push time.
+- The overall progress bar shows an ETA based on the average speed of the whole run so far, updating live during each upload.
+- `--use-lfs` stores files over 100 MiB with Git LFS during the run, without committing any LFS config, and removes the local setup afterwards.
+- `--report FILE` writes a machine-readable JSON summary of every run.
+- `--notify` and `--notify-webhook` tell you when a run ends, via a desktop notification or a web hook.
+- `commitrocket doctor` checks Git, git-lfs, your settings, the remote and the repository before a run.
+- Settings can be saved in `commitrocket.toml` or `[tool.commitrocket]` in `pyproject.toml`.
+- `--include`, `--exclude`, `--include-from`, `--exclude-from` and `.commitrocketignore` choose which files are handled, using `.gitignore`-style patterns.
+- `--remote` and `--branch` choose where to push, `--no-push` only commits, and `--message-template` customises commit messages.
+- `--lfs-commit-rules` commits LFS rules per file type so clones get the real files.
+- A failed `--use-lfs` run now keeps the LFS hooks until its commits are pushed, so LFS files are never published as bare pointers.
+- `--repo` now defaults to the current folder.
+- A `--log-file` or `--report` inside the repository is no longer committed, which previously made a run commit its own log forever.
+- `--dry-run` shows the planned batches and commit messages without changing anything.
+- Failed pushes are retried with growing waits (`--retries`, default 3); rejections are not retried.
+- Interrupted or failed runs can be resumed by running the same command again.
+- `--post-buffer-mib` raises Git's HTTP buffer for large pushes over HTTPS.
+- Each push is checked against the remote, and LFS files are confirmed as pointers before upload.
+- `--lfs-threshold-mib` sets the size above which `--use-lfs` applies (default 100); `0` sends every file through LFS.
+- Each run writes a log file to the system's standard log folder; `--level` sets the detail and `--log-file` overrides the location.
+- `--batch-type` chooses how files are grouped: `deterministic` (default, unchanged), `sequential` or `soft`.
+- `--compression-threads`, `--lfs-threads` and `--lfs-batch-mib` speed up pushes; the thread settings apply to the repository only and are restored afterwards.
+- Leftover local commits containing files over 100 MiB are detected at startup, with the command to clean them up.