Repository navigation
Build-file change alert — live demo - #3
Code-delta-support wants to merge 6 commits into
Conversation
Adds an inert build-demo/ sample (Makefile, Dockerfile, docker-compose, .gitlab-ci.yml, autoconf m4, debian packaging, go.sum, a hooked setup.py and C sources), adds an inert postinstall to the churn-demo sample package.json, and removes the old-side package.json — so the CodeDelta Action's PR comment shows the Build files changed alert: install hooks first, ADDED/MODIFIED statuses, and a deleted dependency manifest. Never to be merged; a live display of the alert.
CodeDelta reportChurn: 329 logical statements (+321 / −8 / Δ0); REP_CHURN 1.00
Agent scan: 64 CRITICAL · 7 HIGH · 81 ELEVATED · 19 endpoint-level · 64 text-level · 3 binary AI signals are pointers for review, not verdicts. Full report attached to this run. CodeDelta 2.3.0. |
…6 example domain) — gives the fetch tier something to flag in this PR's diff; inert, nothing is ever fetched
A permanent display PR for the v1.9.6 build-file change alert — not for merging.
This diff changes the project's build surface on purpose: a Makefile, Dockerfile, docker-compose, GitLab CI file, autoconf m4 macro and debian packaging are added; a setup.py with an install-time cmdclass hook is added; the sample package.json gains a postinstall script (install hook); and a dependency manifest is deleted. All content is inert sample code.
The CodeDelta Action comment below shows how the alert reports it: install hooks first, per-file ADDED/MODIFIED status, dependency manifests as the quieter line.