chore(Action): update action add any-of-labels config

[ArgoZhang]

Link issues

fixes #5719

Summary By Copilot

This pull request includes updates to the .github/workflows/close-stale-issues.yml file to modify the schedule for closing inactive issues and to adjust the configuration for handling stale issues. The most important changes include updating the cron schedule and refining the labels and messages used for stale issues.

Changes to the cron schedule:

• .github/workflows/close-stale-issues.yml: Changed the cron schedule from "30 2 * * *" to "0 1 * * *" to adjust the timing for closing inactive issues.

Refinements to stale issue handling:

• .github/workflows/close-stale-issues.yml: Added any-of-labels parameter with values "invalid,need-repro-project" to specify labels that trigger the stale issue process.
• .github/workflows/close-stale-issues.yml: Updated the stale-issue-message and close-issue-message to include a carriage return for better formatting.

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

Updates the close-stale-issues workflow to run at a different time and to consider issues with the 'invalid' or 'need-repro-project' labels as stale.

CI:

• Updates the cron schedule for the close-stale-issues workflow.
• Configures the close-stale-issues workflow to consider issues with the 'invalid' or 'need-repro-project' labels as stale.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the .github/workflows/close-stale-issues.yml file to modify the schedule for closing inactive issues and to adjust the configuration for handling stale issues. The cron schedule was updated, and the configuration for handling stale issues was adjusted by adding the any-of-labels parameter and updating the stale-issue-message and close-issue-message.

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

File-Level Changes

Change	Details	Files
The cron schedule for closing inactive issues was updated.	The cron schedule was changed from '30 2 * * *' to '0 1 * * *'.	.github/workflows/close-stale-issues.yml
The configuration for handling stale issues was adjusted.	The any-of-labels parameter was added with values 'invalid,need-repro-project'. The stale-issue-message and close-issue-message were updated to include a carriage return for better formatting.	.github/workflows/close-stale-issues.yml

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#5719	Update the action to add any-of-labels configuration.	✅

Possibly linked issues

• chore(Action): update action add any-of-labels config #5719: The PR updates the action with any-of-labels config as requested in the issue.

---

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 whether the any-of-labels configuration should be configurable via repository settings instead of hardcoding it in the workflow.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 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.}

[sourcery-ai]

question: Review the use of '\r' in the message strings.

The added carriage return ('\r') might affect formatting. Consider whether a newline ('\n') might be more appropriate, or confirm that the carriage return produces the desired layout in all environments.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (4182636) to head (66a1c2f).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #5720   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          657       657           
  Lines        29830     29830           
  Branches      4229      4229           
=========================================
  Hits         29830     29830           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.