Renovate DRY

[edmundmiller]

Removes all the stuff that's duplicated at https://github.com/nf-core/ops/blob/main/.github/renovate/default.json5

Even if you automerge PRs, you are likely to still get notification noise - one when the PR is created and another when it is merged. For this reason we recommend you consider setting automergeType=branch which will mean:

• Renovate first creates a branch and no PR
• If tests pass, Renovate pushes a commit directly to the base branch without PR
• If tests fail, Renovate raises a PR for you to review

Add the renovate/** branch to your testing workflow files, or Renovate will not work properly with the automergeType=branch setting.

[mashehu]

We don't allow direct pushes to the dev branch, so not sure if that automerge here will work.

[edmundmiller]

I think we can all renovate both to by pass that(according to their docs)

[edmundmiller]

This is what we'd need to enable(didn't save the config)

[SPPearce]

So are we planning on changing the settings?

[edmundmiller]

Unless anyone states otherwise, but I'd need someone else to at-least approve the PR.

[mirpedrol]

Where are we setting automergeType=branch?

[mashehu]

I personally don't like an automerge for version updates. I would still prefer a PR per update even if we always accept them. But it allows a bit better oversight what has been changed.

[SPPearce]

If it can stop spamming PRs like #5757 that'd be good