In our company it happens often that people onboard renovate on a repository and later move on to other projects and just ignore any renovate interaction with the old repository... This creates quite a lot of unneeded work for renovate where no user reacts to anything renovate does. It would be nice if renovate could "pause" its work on repositories without "activity".
Aside: This might be hard to detect. On GitLab every project has a last_activity_at field, but that might include activity by "bots", so commits or issue edits by Renovate itself might count as "activity". Perhaps Renovate could keep track of the last time a user "interacted" with Renovate (merged/closed a MR, checked a checkbox in any issue/MR, etc.) and count that as "last activity".
In our company it happens often that people onboard renovate on a repository and later move on to other projects and just ignore any renovate interaction with the old repository... This creates quite a lot of unneeded work for renovate where no user reacts to anything renovate does. It would be nice if renovate could "pause" its work on repositories without "activity".
Aside: This might be hard to detect. On GitLab every project has a
last_activity_at
field, but that might include activity by "bots", so commits or issue edits by Renovate itself might count as "activity". Perhaps Renovate could keep track of the last time a user "interacted" with Renovate (merged/closed a MR, checked a checkbox in any issue/MR, etc.) and count that as "last activity".