Automerge devDependencies

[nzakas]

To cut down on the amount of manual intervention we need on repos, what do you think about enabling automerge for devDependencies and GitHub actions?

Assuming CI passes, I think these should be safe.

[lumirlumir]

I'm personally 👍 on adopting auto-merge for devDependencies and GitHub Actions.

I think this could reduce the time spent on manual merging. @aladdin-add What do you think?

---

According to the Renovate documentation, there's an automerge option, and the setup looks straightforward.

Ref: https://docs.renovatebot.com/key-concepts/automerge/

I can work on it if accepted.

[aladdin-add]

👍 to non-major dependencies (including dev) updates; for major updates, manual confirmation is preferable.

[aladdin-add]

another point: if automatic merging is allowed, it seems that grouping dev deps is no longer necessary?

[lumirlumir]

I think retaining grouped dev-dependencies still makes sense, since if two or more dev-dependencies are released around the same time they can still be grouped. But, I don't have a strong opinion on this.

[nzakas]

Let's keep grouping. The goal here is to minimize the number of PRs that fill up notifications.

And to be clear: this is just for devDependencies. We'd need to have a separate discussion about regular dependencies, but I think we should wait to see how it works with devDependencies first.

[lumirlumir]

Okay — it seems there's consensus on the approach we should take here. I'm marking it as accepted.

[eslint-github-bot]

👋 Hi! This issue is being addressed in pull request #49. Thanks, @lumirlumir!