whycode-cli 0.2.0__tar.gz → 0.2.1__tar.gz

{whycode_cli-0.2.0/src/whycode_cli.egg-info → whycode_cli-0.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: whycode-cli
-Version: 0.2.0
+Version: 0.2.1
 Summary: Tells you what to be afraid of before you touch a file.
 Author: Kevin
 License-Expression: MIT
@@ -67,13 +67,14 @@ decide what to do.
 
 ## Install
 
-Once published to PyPI:
-
 ```bash
-pip install whycode
+pip install whycode-cli
 ```
 
-From source (current canonical path):
+The PyPI distribution is `whycode-cli` (the bare name `whycode` was already
+taken by an unrelated project); the installed command is still `whycode`.
+
+From source, if you want to track `main`:
 
 ```bash
 pip install git+https://github.com/fangshuor/WhyCode.git
@@ -177,11 +178,13 @@ That installs two things:
 - **`.git/hooks/pre-commit`** — runs `whycode diff --staged --fail-on handle`
   before every commit. HANDLE WITH CARE files can't be touched without an
   explicit `git commit --no-verify`.
-- **`.github/workflows/whycode.yml`** — a GitHub Action that risk-ranks every
-  PR's files and fails the build at `--fail-on history` (≥ READ HISTORY FIRST).
+- **`.github/workflows/whycode.yml`** — a GitHub Action that prints a
+  risk-ranked table for every PR. Advisory by default (never blocks merging);
+  append `--fail-on history` (or `handle` / `look`) to the diff line to turn
+  it into a hard gate.
 
-Tune the `--fail-on` thresholds inside those two files for your repo. Re-run
-with `whycode init --force` to overwrite.
+Tune the thresholds inside those two files for your repo. Re-run with
+`whycode init --force` to overwrite.
 
 **MCP server** — see the next section.
 

{whycode_cli-0.2.0 → whycode_cli-0.2.1}/README.md

@@ -39,13 +39,14 @@ decide what to do.
 
 ## Install
 
-Once published to PyPI:
-
 ```bash
-pip install whycode
+pip install whycode-cli
 ```
 
-From source (current canonical path):
+The PyPI distribution is `whycode-cli` (the bare name `whycode` was already
+taken by an unrelated project); the installed command is still `whycode`.
+
+From source, if you want to track `main`:
 
 ```bash
 pip install git+https://github.com/fangshuor/WhyCode.git
@@ -149,11 +150,13 @@ That installs two things:
 - **`.git/hooks/pre-commit`** — runs `whycode diff --staged --fail-on handle`
   before every commit. HANDLE WITH CARE files can't be touched without an
   explicit `git commit --no-verify`.
-- **`.github/workflows/whycode.yml`** — a GitHub Action that risk-ranks every
-  PR's files and fails the build at `--fail-on history` (≥ READ HISTORY FIRST).
+- **`.github/workflows/whycode.yml`** — a GitHub Action that prints a
+  risk-ranked table for every PR. Advisory by default (never blocks merging);
+  append `--fail-on history` (or `handle` / `look`) to the diff line to turn
+  it into a hard gate.
 
-Tune the `--fail-on` thresholds inside those two files for your repo. Re-run
-with `whycode init --force` to overwrite.
+Tune the thresholds inside those two files for your repo. Re-run with
+`whycode init --force` to overwrite.
 
 **MCP server** — see the next section.
 

{whycode_cli-0.2.0 → whycode_cli-0.2.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "whycode-cli"
-version = "0.2.0"
+version = "0.2.1"
 description = "Tells you what to be afraid of before you touch a file."
 readme = "README.md"
 license = "MIT"

{whycode_cli-0.2.0 → whycode_cli-0.2.1}/src/whycode/__init__.py

@@ -1,3 +1,3 @@
 """WhyCode — tells you what to be afraid of before touching a file."""
 
-__version__ = "0.2.0"
+__version__ = "0.2.1"

whycode_cli-0.2.1/src/whycode/templates/github-workflow.yml

@@ -0,0 +1,40 @@
+# Risk-rank pull requests with WhyCode.
+#
+# On every PR this workflow computes the Risk Card for each changed file
+# (vs the PR base) and prints a risk-ranked table to the job log.
+# Advisory by default — humans decide.
+#
+# To turn it into a hard gate that blocks merging, append `--fail-on <band>`
+# to the `whycode diff` line below:
+#   handle    block at HANDLE WITH CARE   (score >= 75)
+#   history   block at READ HISTORY FIRST (score >= 50)
+#   look      stricter — block at >= 25
+name: WhyCode
+
+on:
+  pull_request:
+    types: [opened, synchronize, reopened]
+
+permissions:
+  contents: read
+  pull-requests: read
+
+jobs:
+  whycode:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out PR
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # WhyCode needs full history
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install WhyCode
+        run: pip install whycode-cli
+
+      - name: Risk-rank files in this PR
+        run: whycode diff --base origin/${{ github.base_ref }}

{whycode_cli-0.2.0 → whycode_cli-0.2.1/src/whycode_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: whycode-cli
-Version: 0.2.0
+Version: 0.2.1
 Summary: Tells you what to be afraid of before you touch a file.
 Author: Kevin
 License-Expression: MIT
@@ -67,13 +67,14 @@ decide what to do.
 
 ## Install
 
-Once published to PyPI:
-
 ```bash
-pip install whycode
+pip install whycode-cli
 ```
 
-From source (current canonical path):
+The PyPI distribution is `whycode-cli` (the bare name `whycode` was already
+taken by an unrelated project); the installed command is still `whycode`.
+
+From source, if you want to track `main`:
 
 ```bash
 pip install git+https://github.com/fangshuor/WhyCode.git
@@ -177,11 +178,13 @@ That installs two things:
 - **`.git/hooks/pre-commit`** — runs `whycode diff --staged --fail-on handle`
   before every commit. HANDLE WITH CARE files can't be touched without an
   explicit `git commit --no-verify`.
-- **`.github/workflows/whycode.yml`** — a GitHub Action that risk-ranks every
-  PR's files and fails the build at `--fail-on history` (≥ READ HISTORY FIRST).
+- **`.github/workflows/whycode.yml`** — a GitHub Action that prints a
+  risk-ranked table for every PR. Advisory by default (never blocks merging);
+  append `--fail-on history` (or `handle` / `look`) to the diff line to turn
+  it into a hard gate.
 
-Tune the `--fail-on` thresholds inside those two files for your repo. Re-run
-with `whycode init --force` to overwrite.
+Tune the thresholds inside those two files for your repo. Re-run with
+`whycode init --force` to overwrite.
 
 **MCP server** — see the next section.
 

whycode_cli-0.2.0/src/whycode/templates/github-workflow.yml

@@ -1,42 +0,0 @@
-# Risk-gates pull requests with WhyCode.
-#
-# On every PR this workflow computes the Risk Card for each changed file
-# (vs the PR base) and:
-#   - prints a risk-ranked table to the job log
-#   - exits non-zero if any file reaches the band you choose, blocking merge
-#
-# Tune `--fail-on` to taste:
-#   handle   block PRs touching files >= HANDLE WITH CARE (>= 75)
-#   history  block PRs touching files >= READ HISTORY FIRST (>= 50)
-#   look     stricter; block at >= 25 (probably too noisy)
-#
-# Remove `--fail-on` entirely to make WhyCode advisory only.
-name: WhyCode
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened]
-
-permissions:
-  contents: read
-  pull-requests: read
-
-jobs:
-  whycode:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Check out PR
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0  # WhyCode needs full history
-
-      - name: Set up Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: "3.11"
-
-      - name: Install WhyCode
-        run: pip install git+https://github.com/fangshuor/WhyCode.git
-
-      - name: Risk-rank files in this PR
-        run: whycode diff --base origin/${{ github.base_ref }} --fail-on history