Overview
Background
We wrote blog posts about how to handle a number of Pull Requests by Renovate automatically.
- 2022-02-18 Renovate の大量の Pull Request を処理する技術
- 2022-03-29 Automate handling a number of Pull Requests by Renovate in Terraform Monorepo
As described in blog posts, leaving Renovate pull requests open will limit the number of new pull requests that can be created. Therefore, you could close pull requests that could not be automerged and delete feature branches automatically.
renovate-issue-action helps you managing tasks as GitHub Issues to handle closed pull requests.
Overview
Please run renovate-issue-action with GitHub Actions triggered by pull_request's closed events.
An Issue is created when Renovate's Pull Request was closed by other than Renovate.
--
--
The issue description has a list of closed Pull Requests. If the issue already exists, closed pull request is added to the list of closed Pull Request instead of creating a new Issue.
If a Pull Request is merged or Renovate closes it, the related issue would be closed.
--
Why don't you use closed Pull Requests instead of Issues?
You could use closed Pull Requests instead of Issues without renovate-issue-action.
Then why do we develop renovate-issue-action?
We think it is inconvenient to treat closed Pull Requests as tasks. Renovate creates a new Pull Request when a new version is released, so there would be multiple Pull Requests against the same task. It is difficult to understand the list of unresolved Pull Requests.