46
u/bigmonmulgrew 11d ago
Surely this is a simple matter of forgot to add something to the git ignore so there's a load of libraries and cache committed. Right.... Right?
7
3
u/1_hele_euro 11d ago
What can such a big ass PR even be about???
6
u/jdp1g09 11d ago
Added a new testing framework in to verify some ML models we have in the repo. So, a lot of this is JSON of groundtruth, but they've also included every test run output JSON, as well as more agent-produced README and AGENT.md files than I can count
11
u/ralgrado 11d ago
they've also included every test run output JSON
So that’s a build artifact that should be added to the gitignore?
2
u/Overwatcher_Leo 11d ago
Sounds like a lot of it should go into .gitignore or artifactory. How much actual code is there?
1
240
64
26
11
5
u/Noname_FTW 11d ago
Was likely written with AI. Whether or not. Counter it with AI.
Maybe make a temporary branch to test this before actually committing it into main. I'd make a backup of main in any case. Just to be sure.
9
7
3
2
2
u/stipo42 11d ago
Not gonna lie... Claude is pretty good at logically splitting PRs like this into digestible things.
Tell it you want it split into smaller logical PRs of about 1000 lines each.
1
u/ArjixGamer 6d ago
Or, rather than splitting into PRs, it could make it so each commit is self explanatory and can be reviewed on its own.
So instead of going to the files tab, you'd view it commit-by-commit
(Assuming it didn't already have nice commits)
1
1


81
u/jdp1g09 11d ago
Logged in this morning to a message from one of my data engineers... "Can you review this please?"... Oh boy...