aboutsummaryrefslogtreecommitdiff
path: root/internal/engine/plan.go
Commit message (Collapse)AuthorAgeFilesLines
* {now} is the start of the run, as the spec always saidLukasz Kasprzak2 days1-1/+9
| | | | | | | | | | | | | The clock was read once per directory, so a run of several directories stamped several different times - and a review that took a few seconds could put one run's files into two folders, or at midnight two dates. The spec (§7.3) says "the start of the run"; krino.conf(5) documented the behaviour rather than the intent, so the two contradicted each other. The session now carries the run's clock and every directory plans with it. Engine.Plan keeps its meaning for a caller with no session of its own; Session.Plan passes the run's own start.
* the module path is git.labunix.xyz/krinoLukasz Kasprzak2 days1-1/+1
| | | | | | | | | | | So that go install can find it. cgit serves no go-import meta tag, so nginx answers a ?go-get=1 request for /NAME with one pointing at https://git.labunix.xyz/NAME.git; the alternative was carrying a .git suffix through every import line forever. One sed over the imports, both go.mod files, and the dependency gate's whitelist. Nothing else depends on the path. go install works from the next tag, the first release whose go.mod carries it.
* explain reports captures and the chain a file would getLukasz Kasprzak4 days1-11/+18
|
* krino: duplicates are found, never deletedLukasz Kasprzak5 days1-1/+1
| | | | | | | | | A rule combining (duplicate) with a delete action is refused at load, and a file that is a duplicate under any duplicate scope its directory uses gets no delete step from any rule: the plan shows it skipped and the chain continues. A failed duplicate check blocks the delete too. Tests cover (matched), another rule's own condition, a test evaluation skipped, two scopes and a failed check, each checking every copy is still on disk.
* krino: planning — chains, placeholders, conflicts, JSONLukasz Kasprzak7 days1-0/+60