Adding a new supported version template for commitHashes

[chouetz]

Tell us more.

Hello!

I would like to use the customManagers of Renovate to bump internal dependencies. In our situation we don't have any versioning and I would just like to bump the latest commit from the target repository.
I've tried to use a customManager/customDatasource (eg below creating a list of one element)

    "my-custom-source": {
      "defaultRegistryUrlTemplate": "https://api.github.com/repos/<owner>/<repo>/branches/<branch>",
      "transformTemplates": [
        "{\"releases\": [{\"version\": $.commit.sha, \"releaseTimestamp\": $.commit.commit.author.date }] }"
      ]
    }

and it seems the commitHashes are ignored on purpose since #6919 (if I use the commit GH API it can work if a hash starts by 6 digit 😄 )
While I fully understand why we would like to dismiss hashes when we want to be able to compare versions, I think being able to bump the latest version (whatever it is) can be a valid use case, not just for me.
As a consequence, would you be ok to add a new commitHash version template specific for this precise use case?
If it is eligible as a version I suppose adding a dedicated folder here should do the trick? If you agree I can do the contribution.

Do not hesitate to redirect me with alternative proposal if any.

Thanks in advance (for your tool and your active support)

[secustor]

Use the git-refs datasource and not a custom datasource.

[chouetz]

Ho great, it works like a charm, thanks a lot for your valuable support!