commit-check-mcp 0.1.2__tar.gz → 0.1.4__tar.gz

commit_check_mcp-0.1.4/.github/dependabot.yml

@@ -0,0 +1,23 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: "monthly"
+    groups:
+      github-actions:
+        patterns:
+          - "*"
+  - package-ecosystem: pip
+    directory: /
+    schedule:
+      interval: "monthly"
+    groups:
+      pip:
+        patterns:
+          - "*"

{commit_check_mcp-0.1.2 → commit_check_mcp-0.1.4}/.github/workflows/main.yml

@@ -39,7 +39,7 @@ jobs:
 
       - name: Upload coverage reports to Codecov
         if: matrix.python-version == '3.12'
-        uses: codecov/codecov-action@v5
+        uses: codecov/codecov-action@v6
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
           slug: commit-check/commit-check-mcp
@@ -65,7 +65,7 @@ jobs:
         run: python -m twine check dist/*
 
       - name: Upload distributions
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-artifact@v7
         with:
           name: dist
           path: dist/*

{commit_check_mcp-0.1.2 → commit_check_mcp-0.1.4}/.github/workflows/publish.yml

@@ -45,13 +45,13 @@ jobs:
           commit-check-mcp --help
 
       - name: Upload distributions
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-artifact@v7
         with:
           name: python-package-distributions
           path: dist/*
 
       - name: Create attestations
-        uses: actions/attest-build-provenance@v3
+        uses: actions/attest-build-provenance@v4
         with:
           subject-path: dist/*
 
@@ -65,7 +65,7 @@ jobs:
       id-token: write
     steps:
       - name: Download distributions
-        uses: actions/download-artifact@v4
+        uses: actions/download-artifact@v8
         with:
           name: python-package-distributions
           path: dist

{commit_check_mcp-0.1.2/src/commit_check_mcp.egg-info → commit_check_mcp-0.1.4}/PKG-INFO

@@ -1,17 +1,28 @@
 Metadata-Version: 2.4
 Name: commit-check-mcp
-Version: 0.1.2
+Version: 0.1.4
 Summary: MCP server exposing commit-check validation tools
-Author: commit-check
+Author-email: Xianpeng Shen <xianpeng.shen@gmail.com>
 License: MIT
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: commit-check<3,>=2.5.0
+Requires-Dist: commit-check<3,>=2.7.0
 Requires-Dist: mcp<2,>=1.27.0
 Provides-Extra: dev
 Requires-Dist: pytest<10,>=9.0.0; extra == "dev"
-Requires-Dist: pytest-cov<7,>=6.0.0; extra == "dev"
+Requires-Dist: pytest-cov<8,>=6.0.0; extra == "dev"
 Dynamic: license-file
 
 # commit-check-mcp
@@ -24,7 +35,7 @@ Dynamic: license-file
 
 Model Context Protocol (MCP) server for [commit-check](https://github.com/commit-check/commit-check).
 
-`commit-check-mcp` exposes `commit-check` as local MCP tools so an MCP client can validate commit messages, branch names, author info, and repository state.
+`commit-check-mcp` exposes `commit-check` as local MCP tools so an MCP client can validate commit messages, branch names, author info, push safety, and repository state.
 
 ## Features
 
@@ -33,9 +44,10 @@ This MCP server exposes commit-check validations as MCP tools:
 - `server_health` — returns server/sdk versions
 - `validate_commit_message` — validates a commit message
 - `validate_branch_name` — validates a branch name or the current repo branch
+- `validate_push_safety` — validates that a push is not a force push
 - `validate_author_info` — validates author name/email or the repo's git author config
 - `validate_commit_context` — runs combined checks in one call
-- `validate_repository_state` — validates latest commit, current branch, and author state for a repo
+- `validate_repository_state` — validates latest commit, current branch, author state, and optional push safety for a repo
 - `describe_validation_rules` — returns the effective config and enabled rules after merging defaults and repo config
 
 All validation tools return the same structured commit-check result shape:
@@ -122,9 +134,10 @@ After the client starts the server, it will expose these tools:
 - `server_health`: returns server, SDK, and dependency versions
 - `validate_commit_message(message, config?, repo_path?, config_path?)`
 - `validate_branch_name(branch?, config?, repo_path?, config_path?)`
+- `validate_push_safety(push_refs?, config?, repo_path?, config_path?)`
 - `validate_author_info(author_name?, author_email?, config?, repo_path?, config_path?)`
 - `validate_commit_context(message?, branch?, author_name?, author_email?, config?, repo_path?, config_path?)`
-- `validate_repository_state(repo_path?, config?, config_path?, include_message?, include_branch?, include_author?)`
+- `validate_repository_state(repo_path?, config?, config_path?, include_message?, include_branch?, include_author?, include_push?)`
 - `describe_validation_rules(config?, repo_path?, config_path?)`
 
 The common optional arguments are:
@@ -164,6 +177,15 @@ Validate the full repository state:
 }
 ```
 
+Validate push safety from git pre-push hook ref metadata:
+
+```json
+{
+  "repo_path": "/path/to/repo",
+  "push_refs": "refs/heads/main abc123 refs/heads/main def456"
+}
+```
+
 Inspect the final merged rules that will be applied:
 
 ```json
@@ -189,6 +211,7 @@ Typical patterns:
 
 - Validate an explicit message with a repository's rules
 - Validate the current repository state without passing message/branch/author values manually
+- Validate push safety using pre-push ref metadata, or check the current branch against its upstream
 - Inspect which rules are actually enabled after config merging
 
 Example payload for a repository-wide validation:
@@ -198,7 +221,8 @@ Example payload for a repository-wide validation:
   "repo_path": "/path/to/repo",
   "include_message": true,
   "include_branch": true,
-  "include_author": true
+  "include_author": true,
+  "include_push": true
 }
 ```
 

commit_check_mcp-0.1.2/PKG-INFO → commit_check_mcp-0.1.4/README.md

@@ -1,19 +1,3 @@
-Metadata-Version: 2.4
-Name: commit-check-mcp
-Version: 0.1.2
-Summary: MCP server exposing commit-check validation tools
-Author: commit-check
-License: MIT
-Requires-Python: >=3.10
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: commit-check<3,>=2.5.0
-Requires-Dist: mcp<2,>=1.27.0
-Provides-Extra: dev
-Requires-Dist: pytest<10,>=9.0.0; extra == "dev"
-Requires-Dist: pytest-cov<7,>=6.0.0; extra == "dev"
-Dynamic: license-file
-
 # commit-check-mcp
 
 [![PyPI version](https://img.shields.io/pypi/v/commit-check-mcp)](https://pypi.org/project/commit-check-mcp/)
@@ -24,7 +8,7 @@ Dynamic: license-file
 
 Model Context Protocol (MCP) server for [commit-check](https://github.com/commit-check/commit-check).
 
-`commit-check-mcp` exposes `commit-check` as local MCP tools so an MCP client can validate commit messages, branch names, author info, and repository state.
+`commit-check-mcp` exposes `commit-check` as local MCP tools so an MCP client can validate commit messages, branch names, author info, push safety, and repository state.
 
 ## Features
 
@@ -33,9 +17,10 @@ This MCP server exposes commit-check validations as MCP tools:
 - `server_health` — returns server/sdk versions
 - `validate_commit_message` — validates a commit message
 - `validate_branch_name` — validates a branch name or the current repo branch
+- `validate_push_safety` — validates that a push is not a force push
 - `validate_author_info` — validates author name/email or the repo's git author config
 - `validate_commit_context` — runs combined checks in one call
-- `validate_repository_state` — validates latest commit, current branch, and author state for a repo
+- `validate_repository_state` — validates latest commit, current branch, author state, and optional push safety for a repo
 - `describe_validation_rules` — returns the effective config and enabled rules after merging defaults and repo config
 
 All validation tools return the same structured commit-check result shape:
@@ -122,9 +107,10 @@ After the client starts the server, it will expose these tools:
 - `server_health`: returns server, SDK, and dependency versions
 - `validate_commit_message(message, config?, repo_path?, config_path?)`
 - `validate_branch_name(branch?, config?, repo_path?, config_path?)`
+- `validate_push_safety(push_refs?, config?, repo_path?, config_path?)`
 - `validate_author_info(author_name?, author_email?, config?, repo_path?, config_path?)`
 - `validate_commit_context(message?, branch?, author_name?, author_email?, config?, repo_path?, config_path?)`
-- `validate_repository_state(repo_path?, config?, config_path?, include_message?, include_branch?, include_author?)`
+- `validate_repository_state(repo_path?, config?, config_path?, include_message?, include_branch?, include_author?, include_push?)`
 - `describe_validation_rules(config?, repo_path?, config_path?)`
 
 The common optional arguments are:
@@ -164,6 +150,15 @@ Validate the full repository state:
 }
 ```
 
+Validate push safety from git pre-push hook ref metadata:
+
+```json
+{
+  "repo_path": "/path/to/repo",
+  "push_refs": "refs/heads/main abc123 refs/heads/main def456"
+}
+```
+
 Inspect the final merged rules that will be applied:
 
 ```json
@@ -189,6 +184,7 @@ Typical patterns:
 
 - Validate an explicit message with a repository's rules
 - Validate the current repository state without passing message/branch/author values manually
+- Validate push safety using pre-push ref metadata, or check the current branch against its upstream
 - Inspect which rules are actually enabled after config merging
 
 Example payload for a repository-wide validation:
@@ -198,7 +194,8 @@ Example payload for a repository-wide validation:
   "repo_path": "/path/to/repo",
   "include_message": true,
   "include_branch": true,
-  "include_author": true
+  "include_author": true,
+  "include_push": true
 }
 ```
 

{commit_check_mcp-0.1.2 → commit_check_mcp-0.1.4}/pyproject.toml

@@ -1,5 +1,5 @@
 [build-system]
-requires = ["setuptools>=77", "setuptools-scm", "wheel"]
+requires = ["setuptools>=77", "setuptools-scm"]
 build-backend = "setuptools.build_meta"
 
 [project]
@@ -9,10 +9,23 @@ readme = "README.md"
 requires-python = ">=3.10"
 license = { text = "MIT" }
 authors = [
-  { name = "commit-check" }
+  { name = "Xianpeng Shen", email = "xianpeng.shen@gmail.com" }
+]
+classifiers = [
+  "Development Status :: 4 - Beta",
+  "Environment :: Console",
+  "Intended Audience :: Developers",
+  "License :: OSI Approved :: MIT License",
+  "Operating System :: OS Independent",
+  "Programming Language :: Python :: 3.10",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Programming Language :: Python :: 3.14",
+  "Topic :: Software Development",
 ]
 dependencies = [
-  "commit-check>=2.5.0,<3",
+  "commit-check>=2.7.0,<3",
   "mcp>=1.27.0,<2"
 ]
 dynamic = ["version"]
@@ -20,7 +33,7 @@ dynamic = ["version"]
 [project.optional-dependencies]
 dev = [
   "pytest>=9.0.0,<10",
-  "pytest-cov>=6.0.0,<7"
+  "pytest-cov>=6.0.0,<8"
 ]
 
 [project.scripts]

{commit_check_mcp-0.1.2 → commit_check_mcp-0.1.4}/src/commit_check_mcp/server.py

@@ -14,7 +14,7 @@ from commit_check import __version__ as commit_check_version
 from commit_check.config_merger import deep_merge, get_default_config, load_toml_config
 from commit_check.engine import ValidationContext, ValidationEngine, ValidationResult
 from commit_check.rule_builder import RuleBuilder, ValidationRule
-from commit_check.rules_catalog import BRANCH_RULES, COMMIT_RULES
+from commit_check.rules_catalog import BRANCH_RULES, COMMIT_RULES, PUSH_RULES
 from mcp.server.fastmcp import FastMCP
 
 from . import __version__
@@ -22,8 +22,8 @@ from . import __version__
 mcp = FastMCP(
     "commit-check-mcp",
     instructions=(
-        "Use these tools to validate commit messages, branch names, and author metadata "
-        "with commit-check."
+        "Use these tools to validate commit messages, branch names, author metadata, "
+        "and push safety with commit-check."
     ),
 )
 
@@ -185,6 +185,28 @@ def _validate_branch(
         )
 
 
+def _validate_push(
+    push_refs: str | None = None,
+    *,
+    config: dict[str, Any] | None = None,
+    repo_path: Path | None = None,
+    config_path: str | None = None,
+) -> dict[str, Any]:
+    """Validate push ref updates against commit-check force-push protection."""
+    cfg = _merge_config(config, repo_path=repo_path, config_path=config_path)
+    cfg.setdefault("push", {})["allow_force_push"] = False
+    with _working_directory(repo_path):
+        return _run_checks(
+            ["no_force_push"],
+            ValidationContext(
+                stdin_text=push_refs,
+                config=cfg,
+                push_upstream_fallback=push_refs is None,
+            ),
+            cfg,
+        )
+
+
 def _validate_author(
     name: str | None = None,
     email: str | None = None,
@@ -373,6 +395,24 @@ def validate_author_info(
     )
 
 
+@mcp.tool()
+def validate_push_safety(
+    push_refs: str | None = None,
+    config: dict[str, Any] | None = None,
+    repo_path: str | None = None,
+    config_path: str | None = None,
+) -> dict[str, Any]:
+    """Validate that a push is not a force push."""
+    normalized_push_refs = push_refs.strip() if isinstance(push_refs, str) else None
+    normalized_repo_path = _normalize_repo_path(repo_path)
+    return _validate_push(
+        normalized_push_refs,
+        config=_normalize_config(config),
+        repo_path=normalized_repo_path,
+        config_path=_normalize_config_path(config_path, normalized_repo_path),
+    )
+
+
 @mcp.tool()
 def validate_commit_context(
     message: str | None = None,
@@ -423,9 +463,10 @@ def validate_repository_state(
     include_message: bool = True,
     include_branch: bool = True,
     include_author: bool = True,
+    include_push: bool = False,
 ) -> dict[str, Any]:
-    """Validate the latest commit, current branch, and git author state of a repository."""
-    if not any([include_message, include_branch, include_author]):
+    """Validate the latest commit, branch, author, and optional push safety state."""
+    if not any([include_message, include_branch, include_author, include_push]):
         raise ValueError("At least one validation target must be enabled")
 
     normalized_repo_path = _normalize_repo_path(repo_path)
@@ -461,6 +502,15 @@ def validate_repository_state(
                 config_path=normalized_config_path,
             )["checks"]
         )
+    if include_push:
+        checks.extend(
+            _validate_push(
+                None,
+                config=normalized_config,
+                repo_path=normalized_repo_path,
+                config_path=normalized_config_path,
+            )["checks"]
+        )
 
     return {
         "status": "fail" if any(c["status"] == "fail" for c in checks) else "pass",
@@ -489,7 +539,9 @@ def describe_validation_rules(
         "commit_check_version": commit_check_version,
         "config": merged_config,
         "supported_checks": list(
-            dict.fromkeys(entry.check for entry in COMMIT_RULES + BRANCH_RULES)
+            dict.fromkeys(
+                entry.check for entry in COMMIT_RULES + BRANCH_RULES + PUSH_RULES
+            )
         ),
         "enabled_rules": rules,
     }

commit_check_mcp-0.1.2/README.md → commit_check_mcp-0.1.4/src/commit_check_mcp.egg-info/PKG-INFO

@@ -1,3 +1,30 @@
+Metadata-Version: 2.4
+Name: commit-check-mcp
+Version: 0.1.4
+Summary: MCP server exposing commit-check validation tools
+Author-email: Xianpeng Shen <xianpeng.shen@gmail.com>
+License: MIT
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: commit-check<3,>=2.7.0
+Requires-Dist: mcp<2,>=1.27.0
+Provides-Extra: dev
+Requires-Dist: pytest<10,>=9.0.0; extra == "dev"
+Requires-Dist: pytest-cov<8,>=6.0.0; extra == "dev"
+Dynamic: license-file
+
 # commit-check-mcp
 
 [![PyPI version](https://img.shields.io/pypi/v/commit-check-mcp)](https://pypi.org/project/commit-check-mcp/)
@@ -8,7 +35,7 @@
 
 Model Context Protocol (MCP) server for [commit-check](https://github.com/commit-check/commit-check).
 
-`commit-check-mcp` exposes `commit-check` as local MCP tools so an MCP client can validate commit messages, branch names, author info, and repository state.
+`commit-check-mcp` exposes `commit-check` as local MCP tools so an MCP client can validate commit messages, branch names, author info, push safety, and repository state.
 
 ## Features
 
@@ -17,9 +44,10 @@ This MCP server exposes commit-check validations as MCP tools:
 - `server_health` — returns server/sdk versions
 - `validate_commit_message` — validates a commit message
 - `validate_branch_name` — validates a branch name or the current repo branch
+- `validate_push_safety` — validates that a push is not a force push
 - `validate_author_info` — validates author name/email or the repo's git author config
 - `validate_commit_context` — runs combined checks in one call
-- `validate_repository_state` — validates latest commit, current branch, and author state for a repo
+- `validate_repository_state` — validates latest commit, current branch, author state, and optional push safety for a repo
 - `describe_validation_rules` — returns the effective config and enabled rules after merging defaults and repo config
 
 All validation tools return the same structured commit-check result shape:
@@ -106,9 +134,10 @@ After the client starts the server, it will expose these tools:
 - `server_health`: returns server, SDK, and dependency versions
 - `validate_commit_message(message, config?, repo_path?, config_path?)`
 - `validate_branch_name(branch?, config?, repo_path?, config_path?)`
+- `validate_push_safety(push_refs?, config?, repo_path?, config_path?)`
 - `validate_author_info(author_name?, author_email?, config?, repo_path?, config_path?)`
 - `validate_commit_context(message?, branch?, author_name?, author_email?, config?, repo_path?, config_path?)`
-- `validate_repository_state(repo_path?, config?, config_path?, include_message?, include_branch?, include_author?)`
+- `validate_repository_state(repo_path?, config?, config_path?, include_message?, include_branch?, include_author?, include_push?)`
 - `describe_validation_rules(config?, repo_path?, config_path?)`
 
 The common optional arguments are:
@@ -148,6 +177,15 @@ Validate the full repository state:
 }
 ```
 
+Validate push safety from git pre-push hook ref metadata:
+
+```json
+{
+  "repo_path": "/path/to/repo",
+  "push_refs": "refs/heads/main abc123 refs/heads/main def456"
+}
+```
+
 Inspect the final merged rules that will be applied:
 
 ```json
@@ -173,6 +211,7 @@ Typical patterns:
 
 - Validate an explicit message with a repository's rules
 - Validate the current repository state without passing message/branch/author values manually
+- Validate push safety using pre-push ref metadata, or check the current branch against its upstream
 - Inspect which rules are actually enabled after config merging
 
 Example payload for a repository-wide validation:
@@ -182,7 +221,8 @@ Example payload for a repository-wide validation:
   "repo_path": "/path/to/repo",
   "include_message": true,
   "include_branch": true,
-  "include_author": true
+  "include_author": true,
+  "include_push": true
 }
 ```
 

{commit_check_mcp-0.1.2 → commit_check_mcp-0.1.4}/src/commit_check_mcp.egg-info/SOURCES.txt

@@ -2,6 +2,8 @@
 LICENSE
 README.md
 pyproject.toml
+uv.lock
+.github/dependabot.yml
 .github/workflows/labeler.yml
 .github/workflows/main.yml
 .github/workflows/publish.yml

commit_check_mcp-0.1.4/src/commit_check_mcp.egg-info/requires.txt

@@ -0,0 +1,6 @@
+commit-check<3,>=2.7.0
+mcp<2,>=1.27.0
+
+[dev]
+pytest<10,>=9.0.0
+pytest-cov<8,>=6.0.0

{commit_check_mcp-0.1.2 → commit_check_mcp-0.1.4}/tests/test_server.py

@@ -50,6 +50,83 @@ def test_validate_commit_context_requires_at_least_one_field() -> None:
         server.validate_commit_context()
 
 
+def test_validate_push_safety_forwards_normalized_values(
+    monkeypatch: pytest.MonkeyPatch,
+) -> None:
+    captured: dict[str, object] = {}
+
+    def fake_validate_push(
+        push_refs: str | None,
+        *,
+        config: dict | None,
+        repo_path: Path | None,
+        config_path: str | None,
+    ):
+        captured["push_refs"] = push_refs
+        captured["config"] = config
+        captured["repo_path"] = repo_path
+        captured["config_path"] = config_path
+        return {"status": "pass", "checks": []}
+
+    monkeypatch.setattr(server, "_validate_push", fake_validate_push)
+
+    result = server.validate_push_safety(
+        " refs/heads/main abc refs/heads/main def ",
+        {"push": {"allow_force_push": True}},
+        repo_path=".",
+    )
+
+    assert result["status"] == "pass"
+    assert captured == {
+        "push_refs": "refs/heads/main abc refs/heads/main def",
+        "config": {"push": {"allow_force_push": True}},
+        "repo_path": Path.cwd().resolve(),
+        "config_path": None,
+    }
+
+
+def test_validate_push_forces_no_force_push_rule(
+    monkeypatch: pytest.MonkeyPatch,
+) -> None:
+    captured: list[dict[str, object]] = []
+
+    def fake_run_checks(check_names, context, config):
+        captured.append(
+            {
+                "check_names": check_names,
+                "stdin_text": context.stdin_text,
+                "push_upstream_fallback": context.push_upstream_fallback,
+                "allow_force_push": config["push"]["allow_force_push"],
+            }
+        )
+        return {"status": "pass", "checks": []}
+
+    monkeypatch.setattr(server, "_run_checks", fake_run_checks)
+
+    result = server._validate_push(None, config={"push": {"allow_force_push": True}})
+    empty_refs_result = server._validate_push(
+        "",
+        config={"push": {"allow_force_push": True}},
+    )
+
+    assert result["status"] == "pass"
+    assert empty_refs_result["status"] == "pass"
+    assert captured == [
+        {
+            "check_names": ["no_force_push"],
+            "stdin_text": None,
+            "push_upstream_fallback": True,
+            "allow_force_push": False,
+        },
+        {
+            "check_names": ["no_force_push"],
+            "stdin_text": "",
+            "push_upstream_fallback": False,
+            "allow_force_push": False,
+        },
+    ]
+
+
 def test_validate_author_info_forwards_normalized_values(
     monkeypatch: pytest.MonkeyPatch,
 ) -> None:
@@ -132,6 +209,7 @@ def test_validate_repository_state_requires_one_enabled_target() -> None:
             include_message=False,
             include_branch=False,
             include_author=False,
+            include_push=False,
         )
 
 
@@ -158,16 +236,31 @@ def test_validate_repository_state_combines_requested_checks(
         assert branch is None
         return {"status": "pass", "checks": [{"check": "branch", "status": "pass"}]}
 
+    def fake_validate_push(
+        push_refs: str | None,
+        *,
+        config: dict | None,
+        repo_path: Path | None,
+        config_path: str | None,
+    ):
+        assert push_refs is None
+        return {
+            "status": "pass",
+            "checks": [{"check": "no_force_push", "status": "pass"}],
+        }
+
     monkeypatch.setattr(server, "_validate_message", fake_validate_message)
     monkeypatch.setattr(server, "_validate_branch", fake_validate_branch)
+    monkeypatch.setattr(server, "_validate_push", fake_validate_push)
 
-    result = server.validate_repository_state(include_author=False)
+    result = server.validate_repository_state(include_author=False, include_push=True)
 
     assert result == {
         "status": "pass",
         "checks": [
             {"check": "message", "status": "pass"},
             {"check": "branch", "status": "pass"},
+            {"check": "no_force_push", "status": "pass"},
         ],
     }
 
@@ -192,5 +285,6 @@ allow_branch_names = ["develop"]
     assert result["config"]["commit"]["require_body"] is True
     assert result["config"]["branch"]["allow_branch_names"] == ["develop"]
     assert "message" in result["supported_checks"]
+    assert "no_force_push" in result["supported_checks"]
     assert result["supported_checks"].count("ignore_authors") == 1
     assert any(rule["check"] == "require_body" for rule in result["enabled_rules"])