chore(Action): add issue check action

[ArgoZhang]

Link issues

fixes #375

Summary By Copilot

This pull request introduces two new GitHub Actions workflows to manage issues in the repository. These workflows automate the process of labeling inactive issues and closing issues that require a reproduction project but have not received a response within a specified time frame.

New GitHub Actions workflows:

• .github/workflows/issue-check-inactive.yml: Adds a workflow to label issues as inactive if there has been no activity for 7 days. This workflow runs every 15 days.
• .github/workflows/issue-close-required.yml: Adds a workflow to close issues labeled with 'need-repro-project' if there has been no response within 3 days. This workflow runs daily.

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Adds two new GitHub Actions workflows to automate issue management: one to label inactive issues and another to close issues awaiting reproduction projects.

CI:

• Adds a workflow to label issues as inactive if there has been no activity for 7 days, running every 15 days.
• Adds a workflow to close issues labeled with 'need-repro-project' if there has been no response within 3 days, running daily.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request introduces two new GitHub Actions workflows to automate issue management. The first workflow labels inactive issues, and the second closes issues awaiting reproduction projects that have not received a response within a specified timeframe.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Implemented a new GitHub Actions workflow to label issues as inactive if there has been no activity for 7 days.	Created a new workflow file. Configured the workflow to run every 15 days. Utilized the actions-cool/issues-helper@v3 action to check for inactive issues. Set the inactive-label to 'inactive'. Set the inactive-day to 7.	.github/workflows/issue-check-inactive.yml
Implemented a new GitHub Actions workflow to close issues labeled with 'need-repro-project' if there has been no response within 3 days.	Created a new workflow file. Configured the workflow to run daily. Utilized the actions-cool/issues-helper@v3 action to close issues. Set the labels to 'need-repro-project'. Set the inactive-day to 3. Configured a body message for the closed issue.	.github/workflows/issue-close-required.yml

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#375	Add a GitHub Action to label inactive issues.	✅
#375	Add a GitHub Action to close issues that require a reproduction project but have not received a response within a specified time frame.	✅

Possibly linked issues

• chore(Action): add issue check action #375: The PR implements the issue by adding two new GitHub Actions workflows to manage issues.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @ArgoZhang - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider adding a step to remove the 'need-repro-project' label when closing the issue in issue-close-required.yml.
• It might be helpful to add a comment to the issue when labeling it as inactive in issue-check-inactive.yml.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}