-
-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renovate naming convention issue #3703
Comments
Could I get a little feedback on what convention to fix it with? Or else I'll try to implement one, and maybe some changes to scripts that assume an exact suffix will need to be adapted if ever it doesn't look exactly as before. |
I tried to read through couple days ago and didn't get much out if it. If the convention is different, but distinguishable from what we use in general, then we can accommodate it in the procedure to sorting out PRs before a release. Obviously, consistency is preferable. |
I asked the other day on what was happening, and I got an answer today: renovatebot/renovate#28516 (reply in thread)
There's a hypothesis on what is going on, and an idea on how to fix it, but I'd like to know what you think we should use as naming convention for it. If we are going to work to tune the config to a very specific style to match the previous behaviour, we might as well choose any desired behaviour and do the change right now.
The text was updated successfully, but these errors were encountered: