From 441396c88bf81f1f38a9a63fb018799eb032d273 Mon Sep 17 00:00:00 2001 From: Matthias Nott <mnott@mnsoft.org> Date: Fri, 10 Apr 2026 16:37:31 +0200 Subject: [PATCH] fix: clean stale entries on carry-forward to new date --- workflows/NewTriage.md | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/workflows/NewTriage.md b/workflows/NewTriage.md index 2219d20..67a6b62 100644 --- a/workflows/NewTriage.md +++ b/workflows/NewTriage.md @@ -261,9 +261,9 @@ **Rules:** 1. **Same date as previous sweep:** Update the existing triage file in-place. Add new finds, update statuses. -2. **New date:** Create a new date folder, create a new triage file, and CARRY FORWARD the entire previous triage file as the base. Then add new finds on top. -3. **Carry-forward means:** Copy the full master list (all tiers, all links, all statuses) from the previous triage into the new file. The new file is the single source of truth. -4. **ALL links must be preserved.** When carrying forward, keep every column including Type and Link. Never strip links when copying tables. +2. **New date:** Create a new date folder, copy the previous triage as base, CLEAN IT, then add new finds on top. +3. **Clean on carry-forward:** Remove entries that are expired/dead links, skipped by user, already applied (move to Applied section), already rejected, or confirmed duplicates. Only carry forward jobs that are still open and actionable. This prevents the file from growing endlessly with stale entries. +4. **ALL links must be preserved** on entries that ARE carried forward. Never strip links when copying tables. ### Finding the previous triage file ```bash -- Gitblit v1.3.1