drep-ai 2.4.0

A local commit gate: runs the linters your repo configures, and sends changed code to an LLM for review
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81

//! The hooks other repositories consume, checked against what 2.0 actually is.
//!
//! `.pre-commit-hooks.yaml` is the one file in this repository whose consumer
//! is somebody else's commit gate. Nothing in the Rust suite reads it, so a
//! flag that stopped being right - or a `language` naming a package that no
//! longer exists - fails in their repository rather than ours. These assertions
//! are deliberately textual: adding a YAML parser to state four facts about a
//! 40-line file is a dependency for no gain.

mod common;

/// The file with its comments stripped.
///
/// The comments explain what each setting replaced - `language: python`,
/// `--strict` - so asserting over the raw text matches the explanation of the
/// old value as if it were still in force.
fn hooks_yaml() -> String {
    common::without_comments(".pre-commit-hooks.yaml")
}

/// 2.0 is a Rust binary. `language: python` builds an isolated environment
/// from the PyPI package that Phase 8 deleted, so a consumer's hook would fail
/// at install time with a pip error naming a package this repository no longer
/// publishes.
#[test]
fn no_published_hook_installs_the_python_package() {
    let yaml = hooks_yaml();
    assert!(
        !yaml.contains("language: python"),
        "a published hook still installs drep as a Python package"
    );
    assert!(
        yaml.contains("language: rust"),
        "the published hooks must build the Rust binary"
    );
}

/// The markdown hook blocks on `error` severity, not on everything.
///
/// The entry was written against 1.x, where the doc checks carried no
/// severity, so `--strict` was the only way to make the hook block. Under the
/// 2.0 scale `--strict` means `--fail-on info`, and over a real repository
/// that is dominated by line length and trailing whitespace - measured at 75
/// findings on this tree, none above `info`. A consumer adopting that hook has
/// commits blocked by line length, and deletes the hook.
#[test]
fn the_markdown_hook_blocks_only_on_error_severity() {
    let yaml = hooks_yaml();
    assert!(
        yaml.contains("drep lint-docs --fail-on error"),
        "the markdown hook must gate at error severity"
    );
    assert!(
        !yaml.contains("--strict"),
        "--strict blocks on info findings, which no consumer wants in a hook"
    );
}

/// A pre-push consumer must use the same cold-review handshake as the native
/// hook. A plain `drep check` can leave Git's already-open SSH connection idle
/// for the entire review and then fail with SIGPIPE when Git resumes it.
#[test]
fn the_published_pre_push_hook_uses_the_push_gate() {
    let yaml = hooks_yaml();
    assert!(
        yaml.contains("drep check --push-gate"),
        "the published pre-push hook must stop after warming a cold review"
    );
}

/// drep's own installed pre-push gate must exercise the same reconnect path it
/// publishes. Otherwise release work can remain green while the shipped hook
/// contract is broken.
#[test]
fn the_repository_pre_push_hook_uses_the_push_gate_too() {
    let yaml = common::without_comments(".pre-commit-config.yaml");
    assert!(
        yaml.contains("entry: ./target/release/drep check --push-gate"),
        "drep must gate itself through the cache-first push path"
    );
}