FlexMeasures / flexmeasures / 30897795489
84%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 175
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 83.807%. Remained the same
30897795489

push

github

web-flow 
Add an advisory agent hook reviewing the files a push adds (#2387)

A file can enter a branch without anyone deciding it should. It has happened
twice recently: .git-exclude reached #2289 through a merge and survived until
review, and a `git add -A` swept scheduling_problem.py into a commit that
imported nothing from it.

Both were additions. Modified files are nearly always deliberate; a brand-new
file nobody mentioned is the one worth a second look. So the hook lists what a
push adds relative to the merge-base, and names the ones that look unintended:
dotfiles, .orig/.rej/.bak debris, scratch-looking names, build artifacts, and
anything outside the usual directories.

Advisory, exits 0. It cannot know intent -- it can only ask whether the
addition was meant, which is a question an agent can answer and a gate cannot.

The base is the tracked upstream when there is one, else origin/main, and it
prints which base it used, so a wrong guess is visible rather than silent.
That matters here: a stacked branch's base changes when its parent merges.

Self-tested both directions. Against a synthetic commit adding .git-exclude,
scratch/local_probe.py and a legitimate module, it flags the first two and
leaves the module and its own files alone; with only a legitimate addition it
lists it and flags nothing.


Claude-Session: https://claude.ai/code/session_01X2jLjsQzwztDc7Nxz1ozmQ

Signed-off-by: F.N. Claessen <claessen@seita.nl>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

17100 of 20404 relevant lines covered (83.81%)

0.84 hits per line

Jobs
ID Job ID Ran Files Coverage
1 30897795489.1 175
83.81
 GitHub Action Run
Source Files on build 30897795489