Add workflow for close stale issue

[XuehaoSun]

User description

Type of Change

feature or bug fix or documentation or validation or others
API changed or not

Description

detail description

Expected Behavior & Potential Risk

the expected behavior that triggered by this PR

How has this PR been tested?

how to reproduce the test (including hardware information)

Dependency Change?

any library dependency introduced or removed

---

PR Type

Enhancement

---

Description

• Add GitHub Action for closing stale issues

• Schedule daily check at 22:30 UTC

• Configure stale and close messages

---

Diagram Walkthrough

flowchart LR
  A["GitHub Action Workflow"] -- "Scheduled daily at 22:30 UTC" --> B["Check for Stale Issues"]
  B -- "Mark as stale after 60 days" --> C["Notify Issue Author"]
  C -- "Close after 7 days of inactivity" --> D["Issue Closed"]

Loading

File Walkthrough

	Relevant files
Enhancement	check-stale-issue.yml Add GitHub Action for stale issue management                          .github/workflows/check-stale-issue.yml Define new workflow named 'Close stale issue' Set permissions for reading contents and writing issues Schedule workflow to run daily at 22:30 UTC Use actions/stale@v10 action Configure stale and close parameters +20/-0

---

[PRAgent4INC]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Version Pinning The action actions/stale@v10 is pinned to a specific version. Consider using a more flexible versioning strategy, such as actions/[email protected], to allow for minor updates without requiring a PR change. - uses: actions/stale@v10

[PRAgent4INC]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Improve message clarity Clarify the stale and close issue messages for better user understanding. Consider specifying the action users need to take to prevent closure. .github/workflows/check-stale-issue.yml [17-18] -stale-issue-message: "This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days." -close-issue-message: "This issue was closed because it has been stalled for 7 days with no activity." +stale-issue-message: "This issue is stale because it has been open 60 days with no activity. To keep it open, please remove the stale label or comment on the issue. Otherwise, it will be closed in 7 days." +close-issue-message: "This issue was closed due to inactivity. It has been stale for 7 days without any updates." Suggestion importance[1-10]: 6 __ Why: The suggestion improves the clarity of the messages, making it clearer what actions users need to take to prevent closure. This enhances user experience.	Low
Security	Verify permissions Ensure that the workflow has the necessary permissions to close issues. The current permissions are set to read contents and write issues, which should be sufficient, but verify that these permissions align with the repository's security policies. .github/workflows/check-stale-issue.yml [3-5] +permissions: + contents: read + issues: write - Suggestion importance[1-10]: 5 __ Why: The suggestion asks to verify the permissions, which is important for security but does not provide a concrete change. The existing permissions seem adequate for the task.	Low