ruff-sync 0.1.0.dev2__tar.gz → 0.1.1.dev1__tar.gz

{ruff_sync-0.1.0.dev2 → ruff_sync-0.1.1.dev1}/.pre-commit-config.yaml

@@ -7,12 +7,13 @@ repos:
       - id: check-yaml
         args: ["--unsafe"]
         exclude: .agents/skills/mkdocs-generation/templates/mkdocs.yml
+      - id: check-toml
       - id: end-of-file-fixer
       - id: trailing-whitespace
       - id: no-commit-to-branch
         args: [--branch, develop, --branch, main]
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: "v0.15.5"
+    rev: "v0.15.6"
     hooks:
       - id: ruff-check
         args: ["--fix"]

ruff_sync-0.1.1.dev1/.pre-commit-hooks.yaml

@@ -0,0 +1,15 @@
+- id: ruff-sync-pull
+  name: ruff-sync-pull
+  description: Pull and apply upstream ruff configuration.
+  entry: ruff-sync pull
+  language: python
+  files: ^(\.ruff\.toml|ruff\.toml|pyproject\.toml)$
+  pass_filenames: false
+
+- id: ruff-sync-check
+  name: ruff-sync-check
+  description: Check if ruff configuration is in sync with upstream.
+  entry: ruff-sync check --semantic
+  language: python
+  files: ^(\.ruff\.toml|ruff\.toml|pyproject\.toml)$
+  pass_filenames: false

{ruff_sync-0.1.0.dev2 → ruff_sync-0.1.1.dev1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ruff-sync
-Version: 0.1.0.dev2
+Version: 0.1.1.dev1
 Summary: Synchronize Ruff linter configuration across projects
 Project-URL: Homepage, https://github.com/Kilo59/ruff-sync
 Project-URL: Documentation, https://kilo59.github.io/ruff-sync/
@@ -54,6 +54,7 @@ Description-Content-Type: text/markdown
 - [Quick Start](#quick-start)
 - [Key Features](#key-features)
 - [Configuration](#configuration)
+- [Pre-commit Integration](#pre-commit-integration)
 - [CI Integration](#ci-integration)
 - [Example Workflow](#example-workflow)
 - [Detailed Check Logic](#detailed-check-logic)
@@ -132,33 +133,59 @@ pip install ruff-sync
 
 ### Usage
 
+**The Basic Sync**
+
+```console
+# Pull rules from a central repository into your current project
+ruff-sync pull https://github.com/my-org/standards
+```
+
+**Persistent Configuration**
+
+```console
+# If configured in pyproject.toml (see Configuration), simply run:
+ruff-sync pull
+```
+
+**Initializing a New Project**
+
 ```console
-# Sync from a GitHub/GitLab repository (root or specific directory)
-ruff-sync https://github.com/my-org/standards
-ruff-sync https://github.com/my-org/standards/tree/main/configs/shared
+# Scaffold a new pyproject.toml if your directory is empty
+ruff-sync pull https://github.com/my-org/standards --init
+```
 
-# Or a direct blob/file URL (auto-converts to raw)
-ruff-sync https://github.com/my-org/standards/blob/main/pyproject.toml
+**Syncing Subdirectories or Specific Files**
 
-# Clone from any git repository (using SSH or HTTP, defaults to --depth 1)
-# You can use the --branch flag to specify a branch (default: main)
-ruff-sync git@github.com:my-org/standards.git
-ruff-sync ssh://git@gitlab.com/my-org/standards.git
+```console
+ruff-sync pull https://github.com/my-org/standards/tree/main/configs/shared
+ruff-sync pull https://github.com/my-org/standards/blob/main/pyproject.toml
+```
 
-# Or if configured in pyproject.toml (see Configuration), simply run:
-ruff-sync
+**Using Git (SSH/HTTP)**
 
+```console
+# Clones efficiently (depth 1, blob:none) to extract the config
+ruff-sync pull git@github.com:my-org/standards.git
+```
+
+**Excluding Specific Rules**
+
+```console
 # Exclude specific sections from being overwritten using dotted paths
-ruff-sync --exclude lint.per-file-ignores lint.ignore
+ruff-sync pull --exclude lint.ignore
+```
+
+**Checking for Drift (CI)**
 
-# Check if your local config is in sync (useful in CI)
+```console
+# Verify local config matches upstream. Exits 1 if out of sync.
 ruff-sync check https://github.com/my-org/standards
 
-# Semantic check — ignore cosmetic differences like comments and whitespace
+# Semantic check — ignores cosmetic differences like comments and whitespace
 ruff-sync check --semantic
 ```
 
-Run `ruff-sync --help` for full details on all available options.
+See the [Usage documentation](https://kilo59.github.io/ruff-sync/usage/) for more detailed examples and advanced workflows.
 
 ## Key Features
 
@@ -223,6 +250,19 @@ path = "config/ruff"
 to = "."
 ```
 
+## Pre-commit Integration
+
+Ensure your configuration is always in sync before every commit. Add this to your `.pre-commit-config.yaml`:
+
+```yaml
+- repo: https://github.com/Kilo59/ruff-sync
+  rev: v0.1.0  # Use the latest version
+  hooks:
+    - id: ruff-sync-check
+```
+
+See the [Pre-commit Guide](https://kilo59.github.io/ruff-sync/pre-commit/) for more details.
+
 ## CI Integration
 
 The `check` command is designed for use in CI pipelines. Add it as a step to catch config drift before it merges:

{ruff_sync-0.1.0.dev2 → ruff_sync-0.1.1.dev1}/README.md

@@ -23,6 +23,7 @@
 - [Quick Start](#quick-start)
 - [Key Features](#key-features)
 - [Configuration](#configuration)
+- [Pre-commit Integration](#pre-commit-integration)
 - [CI Integration](#ci-integration)
 - [Example Workflow](#example-workflow)
 - [Detailed Check Logic](#detailed-check-logic)
@@ -101,33 +102,59 @@ pip install ruff-sync
 
 ### Usage
 
+**The Basic Sync**
+
+```console
+# Pull rules from a central repository into your current project
+ruff-sync pull https://github.com/my-org/standards
+```
+
+**Persistent Configuration**
+
+```console
+# If configured in pyproject.toml (see Configuration), simply run:
+ruff-sync pull
+```
+
+**Initializing a New Project**
+
 ```console
-# Sync from a GitHub/GitLab repository (root or specific directory)
-ruff-sync https://github.com/my-org/standards
-ruff-sync https://github.com/my-org/standards/tree/main/configs/shared
+# Scaffold a new pyproject.toml if your directory is empty
+ruff-sync pull https://github.com/my-org/standards --init
+```
 
-# Or a direct blob/file URL (auto-converts to raw)
-ruff-sync https://github.com/my-org/standards/blob/main/pyproject.toml
+**Syncing Subdirectories or Specific Files**
 
-# Clone from any git repository (using SSH or HTTP, defaults to --depth 1)
-# You can use the --branch flag to specify a branch (default: main)
-ruff-sync git@github.com:my-org/standards.git
-ruff-sync ssh://git@gitlab.com/my-org/standards.git
+```console
+ruff-sync pull https://github.com/my-org/standards/tree/main/configs/shared
+ruff-sync pull https://github.com/my-org/standards/blob/main/pyproject.toml
+```
 
-# Or if configured in pyproject.toml (see Configuration), simply run:
-ruff-sync
+**Using Git (SSH/HTTP)**
 
+```console
+# Clones efficiently (depth 1, blob:none) to extract the config
+ruff-sync pull git@github.com:my-org/standards.git
+```
+
+**Excluding Specific Rules**
+
+```console
 # Exclude specific sections from being overwritten using dotted paths
-ruff-sync --exclude lint.per-file-ignores lint.ignore
+ruff-sync pull --exclude lint.ignore
+```
+
+**Checking for Drift (CI)**
 
-# Check if your local config is in sync (useful in CI)
+```console
+# Verify local config matches upstream. Exits 1 if out of sync.
 ruff-sync check https://github.com/my-org/standards
 
-# Semantic check — ignore cosmetic differences like comments and whitespace
+# Semantic check — ignores cosmetic differences like comments and whitespace
 ruff-sync check --semantic
 ```
 
-Run `ruff-sync --help` for full details on all available options.
+See the [Usage documentation](https://kilo59.github.io/ruff-sync/usage/) for more detailed examples and advanced workflows.
 
 ## Key Features
 
@@ -192,6 +219,19 @@ path = "config/ruff"
 to = "."
 ```
 
+## Pre-commit Integration
+
+Ensure your configuration is always in sync before every commit. Add this to your `.pre-commit-config.yaml`:
+
+```yaml
+- repo: https://github.com/Kilo59/ruff-sync
+  rev: v0.1.0  # Use the latest version
+  hooks:
+    - id: ruff-sync-check
+```
+
+See the [Pre-commit Guide](https://kilo59.github.io/ruff-sync/pre-commit/) for more details.
+
 ## CI Integration
 
 The `check` command is designed for use in CI pipelines. Add it as a step to catch config drift before it merges:

{ruff_sync-0.1.0.dev2 → ruff_sync-0.1.1.dev1}/docs/ci-integration.md

@@ -72,26 +72,9 @@ ruff-sync-check:
 
 ---
 
-## 🛠️ Pre-commit Integration
-
 You can use `ruff-sync` with `pre-commit` to ensure your configuration is always in sync before pushing.
 
-Add this to your `.pre-commit-config.yaml`:
-
-```yaml
-repos:
-  - repo: local
-    hooks:
-      - id: ruff-sync-check
-        name: ruff-sync-check
-        entry: uvx ruff-sync check --semantic
-        language: system
-        files: ^pyproject\.toml$
-        pass_filenames: false
-```
-
-!!! note
-    Running `ruff-sync check` in pre-commit is fast because it only performs a network request if the local `pyproject.toml` is older than the upstream or if no cache exists.
+See the [Pre-commit Guide](pre-commit.md) for details on using the official hooks.
 
 ---
 
@@ -101,6 +84,12 @@ repos:
 
 In CI, you usually only care about the functional configuration. Using `--semantic` ensures that minor formatting changes don't break your builds, while still guaranteeing that the actual rules are identical.
 
+### Handle Exclusions Properly
+
+If your project intentionally diverges from the upstream (e.g., using different `per-file-ignores` or ignoring a specific rule), ensure those overrides are listed in the `[tool.ruff-sync]` `exclude` list in your `pyproject.toml`.
+
+The `check` command respects your local `exclude` list. If you exclude a setting, `ruff-sync check` will completely ignore it when comparing against the upstream, ensuring that intended deviations never cause CI to fail!
+
 ### Use a Dedicated Workflow
 
 Running `ruff-sync` as a separate job in your linting workflow makes it easy to identify when a failure is due to configuration drift rather than a code quality issue.

{ruff_sync-0.1.0.dev2 → ruff_sync-0.1.1.dev1}/docs/configuration.md

@@ -60,16 +60,19 @@ exclude = ["target-version"]
 
 #### Sequential merging of multiple sources
 
-You can specify multiple upstream sources as a list. They will be merged in order, with later sources overriding earlier ones.
+You can specify multiple upstream sources as a list. They will be merged in order—from top to bottom—with later sources overriding or extending earlier ones.
 
 ```toml
 [tool.ruff-sync]
 upstream = [
-    "https://github.com/my-org/shared-config",
-    "https://github.com/my-org/team-overrides",
+    "https://github.com/my-org/shared-config",  # 1. Base rules
+    "https://github.com/my-org/team-overrides", # 2. Team-specific tweaks (wins)
 ]
 ```
 
+!!! tip "Last One Wins"
+    The merge logic follows a "last one wins" approach for simple keys (like `line-length`), while performing a deep merge for configuration tables like `lint.per-file-ignores`.
+
 ## Deprecation Notes
 
 - The key `source` in `[tool.ruff-sync]` is deprecated and will be removed in a future version. Use `to` instead.

{ruff_sync-0.1.0.dev2 → ruff_sync-0.1.1.dev1}/docs/index.md

@@ -13,11 +13,13 @@
 ## 🚀 Key Features
 
 * **⚡ Fast & Lightweight**: Zero-config needed for most projects.
-* **✨ Formatting Preserved**: Uses `tomlkit` to keep your comments, indentation, and whitespace exactly as they are.
-* **🛡️ Smart Merging**: Safely merges nested tables (like `lint.per-file-ignores`) without overwriting local overrides.
+* **✨ Formatting Preserved**: Keeps all comments and whitespace via `tomlkit`.
+* **🛡️ Smart Merging**: Safely merges nested tables without overwriting local overrides.
 * **📂 Upstream Layers**: Combine and merge configurations from several sources sequentially.
-* **🔗 Flexible Sources**: Sync from GitHub, GitLab, raw URLs, or local files.
-* **✅ CI Ready**: Built-in `check` command with semantic diffs for automated pipelines.
+* **🌐 Flexible Sources**: Sync from GitHub, GitLab, raw URLs, or local files.
+* **📥 Efficient Git Support**: Shallow clones and sparse checkouts for fast extraction.
+* **🚀 Zero-Config Bootstrapping**: Use `--init` to scaffold a new project in one command.
+* **✅ CI Ready**: Built-in `check` command with semantic comparison logic.
 
 ---
 
@@ -38,16 +40,26 @@ Internal "base" configurations or shared presets often fall out of sync, or requ
 
 ## 🏁 Quick Start
 
-### 1. Configure your project
+### 1. Initialize a new project (Optional)
 
-Add the upstream URL to your `pyproject.toml`:
+If your local directory doesn't have a configuration file yet, you can fetch the standard and create one instantly:
+
+```bash
+uv run ruff-sync pull https://github.com/my-org/standards --init
+```
+
+### 2. Configure an existing project
+
+Add the upstream URL to your `pyproject.toml` to make it the default:
 
 ```toml
 [tool.ruff-sync]
 upstream = "https://github.com/my-org/standards/blob/main/pyproject.toml"
 ```
 
-### 2. Pull the configuration
+### 3. Pull the configuration
+
+Once configured, simply run:
 
 ```bash
 uv run ruff-sync pull

ruff_sync-0.1.1.dev1/docs/pre-commit.md

@@ -0,0 +1,69 @@
+# Pre-commit Integration
+
+Using `ruff-sync` with [pre-commit](https://pre-commit.com/) ensures that your Ruff configuration stays in sync with your organization's standards automatically.
+
+## Official Hooks
+
+`ruff-sync` provides two official hooks:
+
+### `ruff-sync-check`
+
+Verifies that your local `pyproject.toml` or `ruff.toml` matches the upstream configuration. It is recommended to use this hook to prevent accidental drift.
+
+```yaml
+- repo: https://github.com/Kilo59/ruff-sync
+  rev: v0.1.0  # Use the latest version
+  hooks:
+    - id: ruff-sync-check
+```
+
+### `ruff-sync-pull`
+
+Automatically pulls and applies the upstream configuration if a drift is detected.
+
+```yaml
+- repo: https://github.com/Kilo59/ruff-sync
+  rev: v0.1.0  # Use the latest version
+  hooks:
+    - id: ruff-sync-pull
+```
+
+## Configuration
+
+The hooks will automatically respect the configuration defined in your `pyproject.toml` under `[tool.ruff-sync]`. Any arguments passed via `args` in `.pre-commit-config.yaml` will override these settings.
+
+> [!NOTE]
+> For a full list of configuration options, see the [Configuration Guide](configuration.md).
+
+### Example `.pre-commit-config.yaml`
+
+```yaml
+repos:
+  - repo: https://github.com/Kilo59/ruff-sync
+    rev: v0.1.0
+    hooks:
+      - id: ruff-sync-check
+        # Common arguments:
+        # --semantic: ignore cosmetic changes (default in check hook)
+        # --no-diff: hide the unified diff
+        # --to PATH: sync to a specific file or directory
+        args: ["--semantic", "--no-diff"]
+```
+
+## Why use `ruff-sync-check`?
+
+Running `ruff-sync check` in pre-commit is fast because:
+
+1. It only checks the `[tool.ruff]` section of the configuration.
+2. It minimizes network overhead by only fetching exactly what it needs (e.g., using direct HTTP requests for single files or partial git cloning for repositories).
+3. By default, it uses `--semantic` to ignore formatting-only differences, reducing false positives.
+
+For more complex scenarios, such as syncing from multiple upstreams or using directory prefixes, see [Advanced Usage](usage.md#advanced-usage).
+
+## Manual Execution
+
+You can always run the hooks manually using:
+
+```bash
+pre-commit run ruff-sync-check --all-files
+```

{ruff_sync-0.1.0.dev2 → ruff_sync-0.1.1.dev1}/docs/troubleshooting.md

@@ -4,6 +4,21 @@ Common issues and questions when using `ruff-sync`.
 
 ## Common Issues
 
+### Debug Logging
+
+If `ruff-sync` is not behaving as expected, you can increase the verbosity of the logs to see what's happening under the hood.
+
+**Usage**:
+
+- `-v`: Shows `INFO` level logs (e.g., which configuration file is being used, where upstreams are being sourced from).
+- `-vv`: Shows `DEBUG` level logs (e.g., detailed TOML merging operations and raw HTTP/Git requests).
+
+Example:
+
+```bash
+ruff-sync pull -vv
+```
+
 ### Upstream URL not found
 
 **Error**: `Error: Upstream Required. No upstream URL found in pyproject.toml or provided as argument.`
@@ -31,6 +46,30 @@ Use the `--exclude` flag to keep your local settings:
 ruff-sync pull --exclude lint.line-length
 ```
 
+### Multi-upstream Fetch Failures
+
+**Error**: `❌ <N> upstream fetches failed`
+
+This happens when one or more of the specified upstream URLs cannot be reached, do not exist, or return an error (e.g., 404 or 403). `ruff-sync` fetches all upstreams concurrently for speed, but requires ALL of them to succeed before it will attempt to merge.
+
+**Solution**:
+1. Check each URL in the terminal output to see which specific one failed.
+2. Verify you have network access and the correct permissions for each source.
+3. If an HTTP source is blocked or private, consider using a Git SSH URL instead.
+
+### Git SSH Workaround for Fetch Errors
+
+If you see an HTTP `403 Forbidden` or `404 Not Found` when trying to fetch from GitHub or GitLab, it might be due to authentication requirements.
+
+**Solution**:
+Use the git-clone alternative suggested in the error message:
+
+```bash
+ruff-sync pull git@github.com:org/repo.git
+```
+
+This uses your local SSH keys and is often more reliable for internal or private repositories.
+
 ## FAQ
 
 ### Does it support `ruff.toml`?

ruff_sync-0.1.1.dev1/docs/usage.md

@@ -0,0 +1,145 @@
+# Usage
+
+`ruff-sync` provides two main commands—`pull` and `check`—designed to keep your Ruff configuration synchronized across projects.
+
+This guide covers common daily workflows, explains how `ruff-sync` merges configuration, and provides a full command reference.
+
+---
+
+## 🌟 Common Workflows
+
+### The Basic Sync
+
+If you want to pull rules from a central repository into your current project, run:
+
+```bash
+ruff-sync pull https://github.com/my-org/standards
+```
+
+This fetches the `pyproject.toml` from the `main` branch of `my-org/standards`, extracts the `[tool.ruff]` section, and surgically merges it into your local `pyproject.toml`.
+
+### Persistent Configuration
+
+Instead of passing the URL every time, you can save the upstream URL in your project's `pyproject.toml`:
+
+```toml
+[tool.ruff-sync]
+upstream = "https://github.com/my-org/standards"
+```
+
+Now, you can simply run:
+
+```bash
+ruff-sync pull
+```
+
+### Initializing a New Project
+
+If your local directory doesn't have a `pyproject.toml` yet, you can scaffold one:
+
+```bash
+ruff-sync pull https://github.com/my-org/standards --init
+```
+
+This creates a new `pyproject.toml` populated with the upstream configuration and automatically adds a `[tool.ruff-sync]` block so you won't need to specify the URL again.
+
+### Syncing Subdirectories
+
+If the upstream repository stores its Python configuration in a specific subdirectory (like a `backend/` folder in a monorepo), use the `--path` argument:
+
+```bash
+ruff-sync pull https://github.com/my-org/standards --path backend
+```
+
+### Excluding Specific Rules
+
+Sometimes your project needs to deviate slightly from the upstream standard. You can exclude specific dotted paths to preserve your local settings:
+
+```bash
+ruff-sync pull --exclude lint.ignore lint.select
+```
+
+*(By default, `lint.per-file-ignores` is always excluded so your local file-specific ignores are safe).*
+
+---
+
+## 🔍 Checking for Drift
+
+To ensure your repository hasn't drifted from your organization's unified standards, use the `check` command. It compares your local config to the upstream and warns you of any divergence.
+
+```bash
+ruff-sync check https://github.com/my-org/standards
+```
+
+*(If you have `upstream` configured in your `pyproject.toml`, you can just run `ruff-sync check`.)*
+
+### Semantic Checking
+
+Often, the exact ordering of keys, whitespace, or comments might slightly differ from the upstream, even though the actual rules are identical. Use the `--semantic` flag to ignore functional equivalents:
+
+```bash
+ruff-sync check --semantic
+```
+
+*(This is heavily recommended for CI pipelines.)*
+
+---
+
+## ✨ Artisanal Merging
+
+One of the core features of `ruff-sync` is its ability to respect your file's existing structure.
+
+Unlike other tools that might blindly overwrite your file, strip away comments, or change indentation, `ruff-sync` uses `tomlkit` to perform a **lossless merge**.
+
+!!! info "What is preserved?"
+    *   **Comments**: All comments in your local file are kept exactly where they are.
+    *   **Whitespace**: Your indentation and line breaks are respected.
+    *   **Key Order**: The order of your existing keys in `[tool.ruff]` is preserved where possible.
+    *   **Non-Ruff Configs**: Any other sections in your `pyproject.toml` (like `[project]` or `[tool.pytest]`) are completely untouched.
+
+---
+
+## 📚 Command Reference
+
+### `pull`
+
+Downloads the upstream configuration and merges it into your local file.
+
+```bash
+ruff-sync pull [UPSTREAM_URL...] [--to PATH] [--exclude KEY...] [--init]
+```
+
+* **`UPSTREAM_URL...`**: One or more URLs to the source `pyproject.toml` or `ruff.toml`. Optional if defined in your local `[tool.ruff-sync]` config. Multiple URLs form a fallback/merge chain. All upstreams are fetched **concurrently**, but they are merged sequentially in the order they are defined. If any upstream fails to fetch, the entire operation will fail.
+* **`--to PATH`**: Where to save the merged config (defaults to the current directory `.`).
+* **`--exclude KEY...`**: Dotted paths of keys to keep local and never overwrite (e.g., `lint.isort`).
+* **`--init`**: Create a new `pyproject.toml` with the upstream configuration if it doesn't already exist.
+
+### `check`
+
+Verifies if your local configuration matches what the upstream would produce. It exits with a non-zero code if differences are found.
+
+```bash
+ruff-sync check [UPSTREAM_URL...] [--semantic] [--diff]
+```
+
+* **`UPSTREAM_URL...`**: The source URL(s). Optional if defined locally.
+* **`--semantic`**: Ignore "non-functional" differences like whitespace, comments, or key order. Only errors if the actual Python-level data differs.
+* **`--diff` / `--no-diff`**: Control the display of the unified diff in the terminal.
+
+---
+
+## 🗺️ Logic Flow
+
+The following diagram illustrates how `ruff-sync` handles the synchronization process under the hood:
+
+```mermaid
+graph TD
+    A[Start] --> B[Resolve all Upstream URLs]
+    B --> C[Fetch all Upstreams Concurrently]
+    C --> D{Any Failures?}
+    D -- Yes --> E[Raise UpstreamError]
+    D -- No --> F[Initialize Target Doc]
+    F --> G[Merge Upstreams Sequentially]
+    G --> H[Save Final Configuration]
+    H --> I[End]
+```

{ruff_sync-0.1.0.dev2 → ruff_sync-0.1.1.dev1}/mkdocs.yml

@@ -8,6 +8,8 @@ edit_uri: edit/main/docs/
 
 theme:
   name: material
+  logo: assets/logo.png
+  favicon: assets/favicon.png
   palette:
     - media: "(prefers-color-scheme: light)"
       scheme: default
@@ -105,8 +107,10 @@ plugins:
 nav:
   - Home: index.md
   - Installation: installation.md
-  - Usage: usage.md
-  - Configuration: configuration.md
-  - CI Integration: ci-integration.md
+  - Usage:
+      - Usage: usage.md
+      - Configuration: configuration.md
+      - Pre-commit: pre-commit.md
+      - CI Integration: ci-integration.md
   - Troubleshooting: troubleshooting.md
   - API Reference: reference/

{ruff_sync-0.1.0.dev2 → ruff_sync-0.1.1.dev1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "ruff-sync"
-version = "0.1.0.dev2"
+version = "0.1.1.dev1"
 description = "Synchronize Ruff linter configuration across projects"
 keywords = ["ruff", "linter", "config", "synchronize", "python", "linting", "automation", "tomlkit"]
 authors = [
@@ -121,7 +121,6 @@ select = [
     # https://beta.ruff.rs/docs/rules/#flake8-datetimez-dtz
     "DTZ", # flake8-datetimez-dtz - prevent use of tz naive datetimes
     "EM", # flake8-errmsg - raw string literals in error messages
-    "ERA", # eradicate - commented-out code
     # https://beta.ruff.rs/docs/rules/#pyflakes-f
     "F", # Pyflakes
     # https://beta.ruff.rs/docs/rules/#pycodestyle-e-w
@@ -197,6 +196,7 @@ ignore = [
     "TRY003", # don't care about long exception messages in tests
     "PLW1510", # subprocess check not needed in tests
     "PT013", # pytest import style, prevents importing param and or types in from style
+    "TC002", # Move third-party import into type-checking block
 ]
 
 [tool.ruff.lint.pydocstyle]