You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Danny McCormick (Jira)" <ji...@apache.org> on 2022/02/06 19:08:00 UTC

[jira] [Updated] (BEAM-13828) Stale bot broken

     [ https://issues.apache.org/jira/browse/BEAM-13828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Danny McCormick updated BEAM-13828:
-----------------------------------
    Fix Version/s: Not applicable
       Resolution: Fixed
           Status: Resolved  (was: Triage Needed)

This is working now - [https://github.com/apache/beam/pull/15938] - it will take a couple weeks for it to work through all the old stale issues though

> Stale bot broken
> ----------------
>
>                 Key: BEAM-13828
>                 URL: https://issues.apache.org/jira/browse/BEAM-13828
>             Project: Beam
>          Issue Type: Bug
>          Components: beam-community
>            Reporter: Danny McCormick
>            Priority: P3
>             Fix For: Not applicable
>
>   Original Estimate: 20m
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Right now stale bot is not running correctly - it looks like it stopped working around a year ago (last pr I could find with stale bot activity). I'm guessing this was unintentionally and broken by probot not being supported anymore, just like the pr labeler (see https://issues.apache.org/jira/browse/BEAM-13779)
>  
> As a consequence of this breakage, we have a lot of stale prs that have been around for a while. As of the writing of this issue, we have 218 prs in the repo, with 129 older than 60 days old (59% stale assuming these don't have more recent activity). This makes the repo feel less active and makes it harder to see the legitimate PRs that have fallen through the cracks. We should fix this by adding the GitHub stale action 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)