Turn the app off after certain period of inaction

[OnkarRuikar]

Issue

Developers install this app and forget about the forks. The app keeps synchronizing those unattended forked repos—for example, https://github.com/jessejay-ch/content/pull/2. The MDN maintainers are still getting spammed with synch notifications, and the fork owner is unresponsive. This also wastes GitHub resources.

At the moment, there are 73,387 unmerged PRs getting rebased till no end and unnecessarily spamming others in the process.

Solution

GitHub turns off the workflows in inactive repos after 60 days.

To prevent unnecessary workflow runs, scheduled workflows may be disabled automatically. When a public repository is forked, scheduled workflows are disabled by default. In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days.

On the same line, could you make the pull app stop updating the sync PRs after a month? This is necessary because the repo owners will not return and will turn off the bot if it is no longer required.

[bot-webhook]

Issue

Developers install this app and forget the forks. And the app keeps synchronizing those unattended forked repos—for example, jessejay-ch/content#2 . The MDN maintainers are still getting spammed with synch notifications, and the fork owner is unresponsive. This also wastes GitHub resources.

Solution

Github turns off the workflows in inactive repos after 60 days.

To prevent unnecessary workflow runs, scheduled workflows may be disabled automatically. When a public repository is forked, scheduled workflows are disabled by default. In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days.

On the same line, could you make the pull app stop updating the sync PRs after a month?

[wei]

Hello, thanks for opening the issue. We will consider this use-case.

Update: Just to clarify, pull is not updating the pull requests. Once created it's updated automatically by GitHub without interactions by pull. Any suggestions welcome!

[dstrome]

We're also running into this situation where abandoned forks are causing nuisance notifications to users in our repos. This really needs to be addressed, please.

[wei]

Just to clarify, pull bot does not send any notifications. The notifications are usually sent by other bots that tag/mention usernames in their replies.

I have implemented conversation locking on any Pull Requests our bot creates which should prevent any bot, including Vercel bot from tagging you and sending you unnecessary notifications. See https://github.com/wei/pull/commit/a5b810cccf43618deb6dc7d75592ca1ce0083ee5