use action/stale instead of probot/stale which has been deprecated.

[fujitatomoya]

• Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

Which issue(s) this PR fixes:

Fixes #746

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

This replaces probot/stale which is not working anymore into action/stale with the same configuration.

• What is the current behavior? (You can also link to an open issue here)

Deprecated, stale workflow is not working anymore for a long time.

• What is the new behavior (if this is a feature change)?

action/stale is online via workflow

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No, only github workflow

• Other information:

[gemini-code-assist]

Summary of Changes

Hello @fujitatomoya, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses the issue of the repository's stale bot no longer functioning due to the deprecation of probot/stale. It migrates the stale issue and pull request management to the action/stale GitHub Action, reactivating the automated process for identifying and closing inactive items. The change ensures that the repository continues to maintain a clean and active issue tracker without altering the existing stale policy.

Highlights

• Stale Bot Migration: Replaced the deprecated probot/stale GitHub App with the action/stale GitHub Action to manage stale issues and pull requests, ensuring the workflow is functional again.
• Configuration Consistency: The new action/stale workflow has been configured to maintain the same rules and settings as the previous probot/stale setup, including days until stale/close and comment messages.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/stale.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to replace the deprecated probot/stale with actions/stale. While it correctly removes the old configuration file .github/stale.yml, it appears to be missing the new GitHub Actions workflow file that would implement actions/stale. As it stands, this PR would remove the stale bot functionality entirely instead of replacing it. Please ensure the new workflow file is included in this pull request to achieve the intended goal.

I am having trouble creating individual review comments. Click here to see my feedback.

.github/stale.yml (1-52)

While removing this configuration file for the deprecated probot/stale is a necessary step, the pull request seems incomplete. The new GitHub Actions workflow file to enable actions/stale is missing. Without it, this PR only removes the stale bot functionality, contrary to its objective of replacing it. Please add the corresponding workflow file (e.g., in .github/workflows/stale.yml) to complete the migration.

[fujitatomoya]

@Shelley-BaoYue @WillardHu what do you think about this? can you take a look?

CC: @kevin-wangzefeng as original author around this area.

[Shelley-BaoYue]

/approve
It looks good to me, we can also make the same modification in other repos.

[kubeedge-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Shelley-BaoYue

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [Shelley-BaoYue]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment