[
https://issues.apache.org/jira/browse/BEAM-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495710#comment-16495710
]
Luke Cwik commented on BEAM-4423:
---------------------------------
It turns out that we need to find a way to differentiate closing PRs from
merging PRs permissions so that Apache is able to point to the source of truth
for where code came from.
Github docs are unclear, write permissions for PRs imply that you can close or
merge PRs with them.
> Automatically clean-up stale pull requests
> ------------------------------------------
>
> Key: BEAM-4423
> URL: https://issues.apache.org/jira/browse/BEAM-4423
> Project: Beam
> Issue Type: Improvement
> Components: build-system
> Reporter: Scott Wegner
> Assignee: Kenneth Knowles
> Priority: Minor
> Labels: github, infra
>
> See conversation on the [dev@
> list|https://lists.apache.org/thread.html/bda552ea7073ca165aaf47034610afafe22d589e386525023d33609e@%3Cdev.beam.apache.org%3E]
> We have many pull requests which have gone inactive for one reason or
> another. These accumulate over time and make it more difficult to track
> active pull requests. The idea is to have some policy and automation around
> cleaning up stale PR's.
> For example:
> * Add a comment after X weeks stating the stale PR policy and that this PR
> will be closed if there is no activity in X days
> * If there is still no activity after X additional days, close the PR.
> We should explore tools that are already built for this, such as
> https://github.com/probot/stale
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
