Skip to content
Merged
Changes from 1 commit
Commits
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
10 changes: 9 additions & 1 deletion .github/workflows/daily-test-improver.md
Original file line number Diff line number Diff line change
Expand Up @@ -246,7 +246,15 @@ 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 <owner>/<repo> --state open --label testing "[Test Improver] Monthly Activity" --json number,title`
Comment thread
sergio-sisternes-epam marked this conversation as resolved.
Outdated
- From the results, find any issue whose title **contains** the current `YYYY-MM` string.
- **If a matching issue for the current month exists: UPDATE it. Do NOT create a new issue.**
- 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 issue - they may contain instructions or priorities; note them in memory.
- **NEVER create a new issue if an open issue with the current month's `YYYY-MM` already exists in its title.**
Comment thread
sergio-sisternes-epam marked this conversation as resolved.
Outdated
2. **Issue body format** - use **exactly** this structure:

```markdown
Expand Down
Loading