krino.git - rule-based file sorter in Go, shows the plan before touching anything, applies only the files you choose, and can undo any run, with s-expression rules and a GTK 4 window

	Commit message (Collapse)	Author	Age	Files	Lines
*	the module path is git.labunix.xyz/krino	Lukasz Kasprzak	46 hours	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \|	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.
*	comments that explain the code, not how it was written	Lukasz Kasprzak	47 hours	1	-24/+24
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	About 340 comments cited the development process: task and plan numbers, fix waves, rulings, reviewers, and the author in the third person with a date. None of that exists outside the work itself, so to a reader it pointed at nothing. Each one now states the engineering reason it was standing in front of; where a comment was provenance and nothing else, it is gone. References to docs/design.md and docs/gui-design.md by section stay: both ship with the repository. The design documents lose their amendment diaries - CHANGELOG.md is that record - and the GUI's says plainly that the window has gone further than the document. Only comments changed. Every .go file was parsed and its code printed with comments stripped, before and after: the two hashes are identical across all 175 files.
*	only where an earlier directory's files ended up stays claimed	Lukasz Kasprzak	4 days	1	-0/+29
\|
*	an earlier directory's applied results stay claimed for later ones	Lukasz Kasprzak	4 days	1	-0/+33
\|
*	tests: apply error exits 1 and w stops krino through the real command; undo ↵	Lukasz Kasprzak	4 days	1	-0/+68
\| \| \| \|	projection occupied half
*	a real run's later directories are not blocked by earlier claims; -n across ↵	Lukasz Kasprzak	4 days	1	-0/+33
\| \| \| \|	directories documented
*	explain: shows a duplicate's skipped delete, leaves the cache alone, walks ↵	Lukasz Kasprzak	4 days	1	-0/+6
\| \| \| \|	only for duplicate tests
*	krino: duplicates are found, never deleted	Lukasz Kasprzak	5 days	1	-24/+77
\| \| \| \| \| \| \| \| \|	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: release 0.0.1 — man pages, install, examples, cross and release, ↵v0.0.1	Lukasz Kasprzak	6 days	1	-0/+63
\| \| \| \| \| \| \| \| \|	README, changelog Also: undo removes the directories its run created; a hardlink is never a duplicate of its own other name; a flag written before "undo" is honoured; --version prints no leading v. Duplicate conditions with different scopes not sharing an original is documented as a known limitation.
*	krino: acting — trash, journal, apply, lock, review, undo	Lukasz Kasprzak	7 days	1	-1/+90
\|
*	krino: matching — scan, ignore, conditions, extraction, duplicates, ↵	Lukasz Kasprzak	7 days	1	-0/+23
	explain, dry run