imap-cleanup-tool 0.1.0__tar.gz

imap_cleanup_tool-0.1.0/.gitattributes

@@ -0,0 +1,4 @@
+# Normalize line endings: store text as LF in the repo, check out native.
+* text=auto eol=lf
+*.bat text eol=crlf
+*.ps1 text eol=crlf

imap_cleanup_tool-0.1.0/.github/workflows/build-and-release.yml

@@ -0,0 +1,67 @@
+name: publish
+
+# Build the package once, then publish it via PyPI Trusted Publishing (OIDC):
+#   * Manual run ("Run workflow" button) -> publishes to TestPyPI.
+#   * Pushing a v* tag                    -> publishes to the real PyPI.
+# No API tokens/secrets are used: the workflow's OIDC identity is the credential,
+# matched against the trusted publisher configured on (Test)PyPI.
+
+on:
+  workflow_dispatch:        # manual button in the Actions tab -> TestPyPI
+  push:
+    tags:
+      - "v*"                # pushing a v* tag -> real PyPI
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.12"
+      - name: Build sdist and wheel
+        run: |
+          python -m pip install --upgrade pip build
+          python -m build
+      - name: Upload the built distributions
+        uses: actions/upload-artifact@v5
+        with:
+          name: dist
+          path: dist/
+
+  publish-testpypi:
+    # Only manual runs publish to TestPyPI (for testing a release).
+    if: github.event_name == 'workflow_dispatch'
+    needs: build
+    runs-on: ubuntu-latest
+    environment: testpypi          # must match the TestPyPI trusted-publisher env
+    permissions:
+      id-token: write              # required to mint the OIDC token
+    steps:
+      - name: Download the built distributions
+        uses: actions/download-artifact@v5
+        with:
+          name: dist
+          path: dist/
+      - name: Publish to TestPyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+
+  publish-pypi:
+    # Only v* tags publish to the real PyPI (the actual release).
+    if: startsWith(github.ref, 'refs/tags/v')
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi              # must match the PyPI trusted-publisher env
+    permissions:
+      id-token: write
+    steps:
+      - name: Download the built distributions
+        uses: actions/download-artifact@v5
+        with:
+          name: dist
+          path: dist/
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

imap_cleanup_tool-0.1.0/.gitignore

@@ -0,0 +1,37 @@
+# Byte-compiled / build artifacts
+__pycache__/
+*.py[cod]
+*.egg-info/
+build/
+dist/
+.eggs/
+
+# Virtual environments
+.venv/
+venv/
+env/
+
+# PyInstaller
+*.spec
+*.manifest
+
+# Tooling
+.pylint.d/
+.pytest_cache/
+.mypy_cache/
+
+# OS / editor
+.DS_Store
+Thumbs.db
+.idea/
+.vscode/
+
+# App data that may be created locally
+*.csv
+targets.txt
+jobs.json
+
+# AI assistant working files (kept local, not published)
+CLAUDE.md
+memory-bank/
+.claude/

imap_cleanup_tool-0.1.0/CLA.md

@@ -0,0 +1,91 @@
+# Contributor License Agreement (CLA)
+
+**Project:** imap-cleanup-tool
+**Project Owner / Licensor:** Giulio Alberello ("the Owner")
+**Contact:** info@giulioalberello.it
+
+Thank you for contributing to imap-cleanup-tool. To keep the project legally
+clean and to let its licensing be managed consistently over time, every
+contributor agrees to this Contributor License Agreement before their
+contribution can be merged. This is a standard mechanism used by many
+open-source projects (for example those maintained under the Apache or Google
+CLA models).
+
+It does **not** take your copyright away: you keep full ownership of your
+contributions and remain free to use them however you like. You simply grant the
+Owner a broad license so the Owner can manage the licensing of the project as a
+whole.
+
+By submitting a contribution (a pull request, patch, or any other work) to this
+project, **you agree to the terms below for that and all your future
+contributions** to the project.
+
+---
+
+## 1. Definitions
+
+- **"You"** means the individual or legal entity making a Contribution.
+- **"Contribution"** means any original work of authorship - including code,
+  documentation, configuration, or assets - that You intentionally submit to the
+  project for inclusion in, or documentation of, the project.
+- **"Submit"** means any form of communication sent to the project (e.g. a pull
+  request, commit, issue attachment, or message), excluding communication
+  conspicuously marked "Not a Contribution".
+
+## 2. Copyright License
+
+You hereby grant **to the Owner** (and to no one else) a **perpetual, worldwide,
+non-exclusive, royalty-free, irrevocable copyright license** to reproduce,
+prepare derivative works of, publicly display, publicly perform, sublicense, and
+distribute Your Contributions and such derivative works, **under any license
+terms the Owner chooses**, including the project's current license, the
+**AGPL-3.0-or-later**.
+
+This means the Owner - and only the Owner - may set and change the terms under
+which the project as a whole is licensed. You retain all right, title, and
+interest in Your Contributions; this is a license grant, **not an assignment** of
+copyright.
+
+## 3. Patent License
+
+You grant the Owner and recipients of the software a **perpetual, worldwide,
+non-exclusive, royalty-free, irrevocable patent license** to make, use, sell,
+offer to sell, import, and otherwise transfer Your Contributions, where such
+license applies only to patent claims licensable by You that are necessarily
+infringed by Your Contribution alone or by combination of Your Contribution with
+the project.
+
+## 4. Your Representations
+
+You represent that:
+
+1. Each Contribution is **Your original creation**, or You have the right to
+   submit it under the terms of this CLA.
+2. If Your employer has rights to intellectual property You create, You have
+   either received permission to make the Contribution on behalf of that
+   employer, or the employer has waived such rights.
+3. Your Contribution does not, to Your knowledge, violate any third party's
+   copyright, patent, trademark, trade secret, or other rights.
+4. You are **legally entitled to grant** the licenses above.
+
+## 5. Developer Certificate of Origin (DCO)
+
+In addition, each commit you submit must certify the
+[Developer Certificate of Origin 1.1](https://developercertificate.org/) by
+adding a `Signed-off-by` line (`git commit -s`). This is a lightweight,
+machine-checkable confirmation of Section 4.
+
+## 6. No Obligation
+
+The Owner is under no obligation to accept or use any Contribution. Contributions
+are provided **"as is"**, without warranty of any kind.
+
+---
+
+> **Not legal advice.** This CLA is a good-faith template for a solo-maintained
+> open-source project. The Owner should have it reviewed by a qualified lawyer in
+> the relevant jurisdiction before relying on it.
+
+**How to agree:** open a pull request; the first time you do, state in a comment
+"I have read the CLA and I agree to it", and sign your commits with `git commit
+-s`. (A bot-enforced CLA check may be added later.)

imap_cleanup_tool-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,66 @@
+# Contributing to imap-cleanup-tool
+
+Thanks for your interest in improving imap-cleanup-tool! Bug reports, fixes, and
+features are welcome.
+
+## Licensing of contributions (important)
+
+This project is published under the **AGPL-3.0**. So that its licensing can be
+managed consistently, **all contributions are accepted under the
+[Contributor License Agreement (CLA)](CLA.md)** - the same approach used by many
+open-source projects.
+
+In short, by submitting a pull request you:
+
+1. **Agree to the [CLA](CLA.md)** - you keep ownership of your work and grant the
+   project owner a broad license to manage the project's licensing.
+2. **Sign off your commits** with the Developer Certificate of Origin:
+
+   ```bash
+   git commit -s -m "your message"      # adds a Signed-off-by line
+   ```
+
+The first time you open a PR, please add a comment: *"I have read the CLA and I
+agree to it."*
+
+## Development setup
+
+```bash
+git clone https://github.com/mrpickles007/imap-cleanup-tool.git
+cd imap-cleanup-tool
+
+python -m venv .venv
+source .venv/bin/activate          # Windows: .venv\Scripts\Activate.ps1
+
+pip install -e ".[dev,web]"        # editable install + dev tools + web UI
+```
+
+## Before you open a PR
+
+- **Run the tests** (standard library only, nothing extra to install):
+
+  ```bash
+  python -m unittest discover -s tests -v
+  ```
+
+- **Add or update tests** for any behavior you change.
+- **Match the codebase conventions** (see [CLAUDE.md](CLAUDE.md) for the golden
+  rules). The most important ones:
+  - **English only** in code, comments, UI strings, and docs.
+  - **CLI and `core.py` stay standard-library only.** Third-party dependencies
+    belong exclusively in the optional `[web]` extra.
+  - **`core.py` is UI-agnostic** - no argument parsing, no presentation.
+  - Preserve the **safety model**: dry-run by default in the web UI,
+    confirmation in the CLI, flag-then-`--expunge`.
+  - Honor **cooperative cancellation** (`should_stop` / `StopRequested`) in
+    long-running code.
+- Keep PRs focused; describe the change and how you tested it.
+
+## Reporting bugs / requesting features
+
+Open a GitHub issue with steps to reproduce (for bugs) or a clear use case (for
+features). Never include real passwords or app passwords in issues or logs.
+
+## Code of conduct
+
+Be respectful and constructive. Harassment or abuse will not be tolerated.