PoC - Staleness action for Element team PRs #5742
Conversation
ouchadam
force-pushed
the
feature/adm/stale-prs
branch
4 times, most recently
from
d87e2bb
to
aeb868a
Compare
ouchadam
force-pushed
the
feature/adm/stale-prs
branch
from
aeb868a
to
dbef6f6
Compare
ouchadam
force-pushed
the
feature/adm/stale-prs
branch
from
dbef6f6
to
59a3d8d
Compare
| @@ -0,0 +1,20 @@ | |||
| name: 'Close stale issues and PRs' | |||
| on: | |||
There was a problem hiding this comment.
this will be swapped to an hourly cron if approved
| steps: | ||
| - uses: sonia-corporation/stale@1.54.0 | ||
| with: | ||
| dry-run: true |
There was a problem hiding this comment.
will be removed if we're happy with the output
| stale: | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: sonia-corporation/stale@1.54.0 |
There was a problem hiding this comment.
uses a staleness action fork to allow for only checking PRs instead of PRs and issues which causes the rate limit to be hit due to our large amount of issues
ouchadam
changed the title
|
I do not like stale bot for PR, or for issues. In the list you have provided, there are a lot of PRs that must finally be merged... We are late to review PRs, but here the sanction is more for the submitter :/ |
1 similar comment
|
I do not like stale bot for PR, or for issues. In the list you have provided, there are a lot of PRs that must finally be merged... We are late to review PRs, but here the sanction is more for the submitter :/ |
|
closing as this can be used as a PoC reference without needing to be open |
Introduces a staleness github action to mark stale and close Element team member PRs