From f3471474e7247afe4f586b124cd8cacfcd859731 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sun, 11 Jan 2026 18:25:08 +0000
Subject: [PATCH 1/3] Initial plan


From dd26adfdec87a3d2ff17e39c1a234aa099b7a3c7 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sun, 11 Jan 2026 18:30:52 +0000
Subject: [PATCH 2/3] Update daily-team-status to use create-issue and close
 older issues

- Changed from create-discussion to create-issue safe-output
- Added close-issue configuration to automatically close older status reports
- Updated workflow description and process steps
- Updated documentation to reflect issue-based reporting

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
---
 docs/daily-team-status.md      |  5 +++--
 workflows/daily-team-status.md | 14 +++++++++-----
 2 files changed, 12 insertions(+), 7 deletions(-)

diff --git a/docs/daily-team-status.md b/docs/daily-team-status.md
index f5893b7..8eb0330 100644
--- a/docs/daily-team-status.md
+++ b/docs/daily-team-status.md
@@ -44,8 +44,9 @@ This workflow requires no configuration and works out of the box. You can use lo
 
 ## What it creates
 
-- Creates new status report issues
-- Updates existing status issues with new information
+- Creates new daily status report issues with the `[team-status]` prefix
+- Automatically closes older status report issues to prevent clutter
+- Labels new issues with `report` and `daily-status` tags
 - Requires `issues: write` permission
 
 ## Human in the loop
diff --git a/workflows/daily-team-status.md b/workflows/daily-team-status.md
index 7b25078..d52de5a 100644
--- a/workflows/daily-team-status.md
+++ b/workflows/daily-team-status.md
@@ -2,7 +2,7 @@
 description: |
   This workflow created daily team status reporter creating upbeat activity summaries.
   Gathers recent repository activity (issues, PRs, discussions, releases, code changes)
-  and generates engaging GitHub discussions with productivity insights, community
+  and generates engaging GitHub issues with productivity insights, community
   highlights, and project recommendations. Uses a positive, encouraging tone with
   moderate emoji usage to boost team morale.
 
@@ -19,14 +19,17 @@ network: defaults
 tools:
   github:
 safe-outputs:
-  create-discussion:
+  create-issue:
     title-prefix: "[team-status] "
-    category: "announcements"
+    labels: [report, daily-status]
+  close-issue:
+    required-title-prefix: "[team-status] "
+    max: 20
 ---
 
 # Daily Team Status
 
-Create an upbeat daily status report for the team as a GitHub discussion.
+Create an upbeat daily status report for the team as a GitHub issue.
 
 ## What to include
 
@@ -44,4 +47,5 @@ Create an upbeat daily status report for the team as a GitHub discussion.
 ## Process
 
 1. Gather recent activity from the repository
-2. Create a new GitHub discussion with your findings and insights
+2. Create a new GitHub issue with your findings and insights
+3. Close older status report issues to keep things tidy

From 947235868808c7a867aee0a1a7b13155c876231f Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sun, 11 Jan 2026 18:35:55 +0000
Subject: [PATCH 3/3] Use close-older-issues field on create-issue instead of
 separate close-issue

- Replaced separate close-issue safe-output with close-older-issues: true on create-issue
- Simplified workflow configuration as requested
- Removed redundant process step

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
---
 workflows/daily-team-status.md | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/workflows/daily-team-status.md b/workflows/daily-team-status.md
index d52de5a..03e4ca8 100644
--- a/workflows/daily-team-status.md
+++ b/workflows/daily-team-status.md
@@ -22,9 +22,7 @@ safe-outputs:
   create-issue:
     title-prefix: "[team-status] "
     labels: [report, daily-status]
-  close-issue:
-    required-title-prefix: "[team-status] "
-    max: 20
+    close-older-issues: true
 ---
 
 # Daily Team Status
@@ -48,4 +46,3 @@ Create an upbeat daily status report for the team as a GitHub issue.
 
 1. Gather recent activity from the repository
 2. Create a new GitHub issue with your findings and insights
-3. Close older status report issues to keep things tidy