adding --include-forked
fails if it's the last argument before floating arguments
#21713
jessehouwing
started this conversation in
Suggest an Idea
Replies: 1 comment
-
The underlying CLI library we use seems a little bit quirky at times, although I'm not sure if they're doing anything wrong. I'm pretty sure that everything works properly if you always put As I mentioned in the PR, we're not wanting those CLI fix-ups to be "permanent" - they're more like hacks. We should probably log a warn whenever commands are migrated so that users are hopefully aware and we can eventually remove them all. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us what version of Renovate you run.
latest
If you're self-hosting Renovate, select which platform you are using.
github.com
If you're self-hosting Renovate, tell us what version of the platform you run.
github
Was this something which used to work for you, and then stopped?
I never saw this working
Describe the bug
I tried to figure out what's going on and there is a special case that causes an issue, which is what I was trying to work around.
When I call
I get an error:
It looks like other booleans don't suffer this fate:
Works just fine, possibly because
--dry-run
is auto migrated to--dry-run=true
.I'm not at all sure how to fix this.
Adding a migration from
--include-forks
to--include-forks=true
fixes the issue, but I'm not sure it's the best way to proceed:--include-forks
is passed, assume=true
#20206Relevant debug logs
Logs
Have you created a minimal reproduction repository?
I have linked to a minimal reproduction repository in the bug description
Beta Was this translation helpful? Give feedback.
All reactions