Skip to content

fix: prevent duplicate Test Improver monthly activity issues #681

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sergio-sisternes-epam wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix: prevent duplicate Test Improver monthly activity issues #681

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0ebad23
fix: prevent duplicate Test Improver monthly activity issues (#658, #…
Apr 12, 2026
478869b
fix: address Copilot review — use ${{ github.repository }} and handle…
Apr 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion .github/workflows/daily-test-improver.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -246,7 +246,17 @@ Always do Task 7 (Update Monthly Activity Summary Issue) every run. In all comme

Maintain a single open issue titled `[Test Improver] Monthly Activity {YYYY}-{MM}` as a rolling summary of all Test Improver activity for the current month.

1. Search for an open `[Test Improver] Monthly Activity` issue with label `testing`. If it's for the current month, update it. If for a previous month, close it and create a new one. Read any maintainer comments - they may contain instructions or priorities; note them in memory.
1. **Find the existing monthly issue (MANDATORY before any create)**:
- Determine the current month string as `YYYY-MM` (e.g. `2025-04`).
- Search for open issues using: `gh search issues --repo ${{ github.repository }} --state open --label testing "[Test Improver] Monthly Activity" --json number,title`
- From the results, collect all open issues whose title **contains** the current `YYYY-MM` string.
- **If exactly one matching issue for the current month exists: UPDATE it. Do NOT create a new issue.**
- **If multiple matching issues for the current month exist: treat the lowest-numbered issue as the canonical monthly issue, UPDATE it, and close every other current-month match as a duplicate of that canonical issue.**
- Before closing duplicate current-month issues, read any maintainer comments on each of them and preserve any instructions or priorities in memory, then consolidate any still-relevant details into the canonical issue update.
- If no matching issue exists for the current month but one exists for a previous month: close the old one, then create a new issue for the current month.
- If no matching issue exists at all: create a new issue for the current month.
- Read any maintainer comments on the canonical issue - they may contain instructions or priorities; note them in memory.
- **NEVER create a new issue if any open issue with the current month's `YYYY-MM` already exists in its title; update the canonical issue and close duplicates instead.**
2. **Issue body format** - use **exactly** this structure:

```markdown
Expand Down
Loading