• No documentation, not sure what is included, very "personal" unfortunately

Yes, that's fair. I'm the main customer here, so very personal indeed. Documentation is here

• Javascript-related configs are mixed in.

The generated project use the python config:

When you make personal changes, all repositories are affected

Yes it's a feature, not a bug 😄

However, in the spirit of making this template more generic to others, I'm open to let users choose a more "default" renovate config, not referencing my own.

I looked a little deeper into your config and have a few questions:

• I am unsure of the need for no-pip-requirements. There is no requirements.txt in the template.
• If boto3, httpx, and sphinx packages are not grouped together, will the automatic updates stop working properly? (And I think these should be configured by the users themselves (except for the deps of sphinx and django (I'm not sure which one are they though)))
• I think github>browniebroke/renovate-configs:automerge can be replaced with config:automergeMinor. (And why not use config:automergeAll?)
• Why not follow Renovate's recommendation and use config:js-lib (or ["config:best-practices", ":pinOnlyDevDependencies"])? In particular, why not follow Renovate's recommendation to pin devDependencies?
• What is the advantage of letting pre-commit.ci update pre-commit dependencies instead of Renovate? Wouldn't it just stop automerge and make it more cumbersome?

python.json

{
  "extends": [
    "github>browniebroke/renovate-configs",
    "github>browniebroke/renovate-configs:cpython",
    "github>browniebroke/renovate-configs:no-pip-requirements",
    "github>browniebroke/renovate-configs:boto3",
    "github>browniebroke/renovate-configs:httpx",
    "github>browniebroke/renovate-configs:sphinx"
  ]
}

default.json

{
  "extends": [
    "config:base", 
    "github>browniebroke/renovate-configs:automerge"
  ],
  "labels": ["dependencies"],
  "pre-commit": {
    "enabled": true
  }
}