jochen 12619ec140 Check that tracking says no event and writes nothing, as ADR 0285 states

2026-10-10 21:51:30 +02:00

..

testdata/hq/04-ISSUES

mesh-issues: import hq's issue folders at their own numbers, and an issue with a folder is whole in the tracker (hq ADR 0275, to-be 53 slice 3)

2026-10-10 16:00:19 +02:00

bus_test.go

mesh-issues: an issue says who works on it, and resolves only from fixing (hq issue 399)

2026-10-10 21:04:32 +02:00

check.go

mesh-issues: triage every new issue — severity, needs, suggested owner, dependencies — and say an issue ready when what it depends on is delivered (hq ADR 0279)

2026-10-10 17:56:08 +02:00

delivery_test.go

mesh-issues: an issue knows whether its fix is delivered, says it ready to verify, and a fix stuck after its merge is said (hq ADR 0281)

2026-10-10 18:12:52 +02:00

delivery.go

mesh-issues: a take-over note records who acted, not the worker named; tests for the remaining rules (hq issue 399)

2026-10-10 21:10:36 +02:00

groom.go

mesh-issues: an issue says who works on it, and resolves only from fixing (hq issue 399)

2026-10-10 21:04:32 +02:00

import_test.go

mesh-issues: import hq's issue folders at their own numbers, and an issue with a folder is whole in the tracker (hq ADR 0275, to-be 53 slice 3)

2026-10-10 16:00:19 +02:00

import.go

mesh-issues: import hq's issue folders at their own numbers, and an issue with a folder is whole in the tracker (hq ADR 0275, to-be 53 slice 3)

2026-10-10 16:00:19 +02:00

issue.go

mesh-issues: an issue says who works on it, and resolves only from fixing (hq issue 399)

2026-10-10 21:04:32 +02:00

main.go

Name issues not closed first, and say a quiet worker before a decision, as ADR 0285 says

2026-10-10 21:50:54 +02:00

manifest_test.go

mesh-issues: an issue knows whether its fix is delivered, says it ready to verify, and a fix stuck after its merge is said (hq ADR 0281)

2026-10-10 18:12:52 +02:00

memory_test.go

mesh-issues: an issue says who works on it, and resolves only from fixing (hq issue 399)

2026-10-10 21:04:32 +02:00

ready.go

mesh-issues: an issue says who works on it, and resolves only from fixing (hq issue 399)

2026-10-10 21:04:32 +02:00

report_test.go

mesh-issues: import hq's issue folders at their own numbers, and an issue with a folder is whole in the tracker (hq ADR 0275, to-be 53 slice 3)

2026-10-10 16:00:19 +02:00

report.go

mesh-issues: an issue says who works on it, and resolves only from fixing (hq issue 399)

2026-10-10 21:04:32 +02:00

tracker_test.go

mesh-issues: a take-over note records who acted, not the worker named; tests for the remaining rules (hq issue 399)

2026-10-10 21:10:36 +02:00

tracker.go

mesh-issues: a take-over note records who acted, not the worker named; tests for the remaining rules (hq issue 399)

2026-10-10 21:10:36 +02:00

tracking_test.go

Check that tracking says no event and writes nothing, as ADR 0285 states

2026-10-10 21:51:30 +02:00

tracking.go

Say in a condition's message which issue tracks it and where that issue stands (issue 400)

2026-10-10 21:44:53 +02:00

triage_test.go

mesh-issues: an issue says who works on it, and resolves only from fixing (hq issue 399)

2026-10-10 21:04:32 +02:00

worker_test.go

mesh-issues: a take-over note records who acted, not the worker named; tests for the remaining rules (hq issue 399)

2026-10-10 21:10:36 +02:00

worker.go

mesh-issues: an issue says who works on it, and resolves only from fixing (hq issue 399)

2026-10-10 21:04:32 +02:00