-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.github/workflows: replace probot-stale with equivalent github action #45230
Conversation
We currently use probot-stale (https://github.com/probot/stale) to mark stale PRs. According to several issues reported for this repository, there is a widespread problem of probot-state not working properly in github projects (i.e. probot/stale#349). Some users recommend using https://github.com/actions/stale instead. Fixes: https://tracker.ceph.com/issues/54443 Signed-off-by: Laura Flores <lflores@redhat.com>
Config based on this recommendation: https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot#example-dependabotyml-file-for-github-actions Signed-off-by: Laura Flores <lflores@redhat.com>
jenkins test windows |
jenkins test make check |
jenkins test api |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for taking care of these things @ljflores !
jenkins test make check |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
jenkins test make check |
@epuertat do you think any permissions need to be explicitly specified as seen here? https://github.com/actions/stale#recommended-permissions
I checked our other github action workflows and didn't see a need for it. But let me know what you think. |
jenkins test windows |
Merging this. I will keep tabs on it to make sure it is working properly as PRs become stale. |
According to the stale bot code (https://github.com/ceph/ceph/blob/master/.github/stale.yml), PRs should become stale automatically after 60 days of inactivity. After 90 days, they should automatically close. This last part is not working properly; PRs are correctly marked stale, but they fail to close after 90 days.
We currently use probot-stale: https://github.com/probot/stale. According to several issues reported for this repository, there is a widespread problem of probot-stale not working properly in github projects (i.e. probot/stale#349). Some users recommend using https://github.com/actions/stale instead.
This PR proposes a switch from probot-stale to the GitHub stale action workflow.
Fixes: https://tracker.ceph.com/issues/54443
Signed-off-by: Laura Flores lflores@redhat.com
Checklist
Show available Jenkins commands
jenkins retest this please
jenkins test classic perf
jenkins test crimson perf
jenkins test signed
jenkins test make check
jenkins test make check arm64
jenkins test submodules
jenkins test dashboard
jenkins test dashboard cephadm
jenkins test api
jenkins test docs
jenkins render docs
jenkins test ceph-volume all
jenkins test ceph-volume tox