Use pre-commit manager with the git-refs datasource

[eyalzek]

What would you like Renovate to be able to do?
we would like to use pre-commit with "bleeding edge versioning", so basically the latest git ref of the pre-commit repo. At the moment the .pre-commit-config.yaml file is being matched by the pre-commit manager which uses the github-tags - although this is the recommended way to go according to pre-commit, we would like to avoid tagging.

Is it actually possible at the moment to override the datasource used by a manager?

[viceice]

Sure, use a package rule, match your deps / manager and assign a new datasource.

[eyalzek]

But how do you assign a new datasource?

"packageRules": [
        {
          "matchManagers": ["pre-commit"],
          "datasource": "git-refs"
        }
]

doesn't seem to work and I can't find a relevant configuration option

[eyalzek]

Oh actually it does work, but the log output still shows github-tags:

"pre-commit": [
  {
    "packageFile": ".pre-commit-config.yaml",
    "deps": [
      {
        "datasource": "github-tags",
        ...
        "versioning": "git"
      }
    ]
  }
]

[viceice]

Yes, the output is before applying any rules. It's just the extract phase. 🤷‍♂️

[raspla]

This does not seem to work with gitlabci-include manager: "validationMessage": "Invalid configuration option: packageRules[0].datasource"

  "packageRules": [
    {
      "matchManagers": ["gitlabci-include"],
      "datasource": "git-refs"
    }
  ]

[eyalzek]

For posterity, considering you have pre-commit file with the following format:

---
repos:
  - repo: git@github.com:foo/bar.git
    rev: xyz
    hooks:
      - id: foo

This is the renovate config that works for update the refs:

{
  "regexManagers": [
        {
          "fileMatch": ["(^|/)\\.pre-commit-config\\.yaml$"],
          "matchStrings": ["repo: (?<depName>.{2,}?)\n\\s+rev: (?<currentDigest>.*?)\n"],
          "datasourceTemplate": "git-refs",
          "versioningTemplate": "git"
        }
  ]
}

[benjamb]

Is there a workaround to make use of git-tags as a datasource with pre-commit? github-tags seems to require an API token to work, which I would prefer to avoid.

Ideally something that doesn't involve using regexManagers like the example above, since that relies on keys being in a specific order, which I can't guarantee.