pre-commit autoupdate --freeze equivalent flag

[l0b0]

What would you like Renovate to be able to do?

pre-commit autoupdate --freeze creates rev: e0f74cfd5f9497d3279995efeb13d11bd6434b5e # frozen: 0.18.4 type entries in .pre-commit-config.yaml. This guarantees reproducibility in case the tag in the upstream repository is moved for any reason.

Should only require a pinDigests flag in the defaultConfig.

If you have any ideas on how this should be implemented, please tell us here.

I'm not very familiar with TypeScript, but I might give this a try.

Is this a feature you are interested in implementing yourself?

Maybe

[github-actions]

Hi there,

Get your issue fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this.

To get started, please read our guide on creating a minimal reproduction.

We may close the issue if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment.

Good luck,

The Renovate team

[rarkins]

This sounds similar conceptually to similar functionality in the github-actions manager

[l0b0]

@rarkins I don't get the reproduction:needed label on this - it's a feature request, not a bug. Is it just a way to close it in two weeks automatically?

[rarkins]

Feature requests are not closed automatically due to lack of reproduction.

But reproductions typically are still required for feature requests, because it's a bad idea to add features without testing them on a real repo first. Sometimes features can be added with just unit tests, but this is not that type of feature.

[l0b0]

But reproductions typically are still required for feature requests, because it's a bad idea to add features without testing them on a real repo first.

Do you mean I need to implement the feature in order to keep this feature request open? If not, could you please explain in more detail?

[rarkins]

I think you misunderstand the meaning of "reproduction". It doesn't mean implementation

[l0b0]

What does it mean, then? I don't think I've ever heard of anyone using "reproduction" is the context of a feature request.

[rarkins]

Please read in full the doc we linked to earlier: https://github.com/renovatebot/renovate/blob/main/docs/development/minimal-reproductions.md

[l0b0]

This seems to be the only relevant line from the documentation:

A minimal reproduction helps the developers see where the bug or missing feature is, and allows us to verify that the new code meets the requirements.

So I guess a reproduction here means pointing out that the relevant code is in lib/modules/manager/pre-commit. Do you need me to be more specific? Is there anything else needed for a "reproduction" of a missing feature? A test?

[rarkins]

It means you create a repository with the minimum content necessary to demonstrate the problem

[l0b0]

I guess we can't get past this communications barrier, so I'd rather just leave it here.