Local platform mode that applies update the the current working directory

[GiuseppeIII]

When running renovate with RENOVATE_PLATFORM=local it would be nice if there would be some way to have whatever changes would normally be made, added to the current working directory (or to a local branch, but that seems to be getting away from platform local and closer to a local mode for a given platform). This would be useful not just for testing, but also when trying to update dependencies locally instead of using each tools own update methods.

I thought

RENOVATE_PLATFORM=local
RENOVATE_DRY_RUN=false

might allow this, but this errors with "message": "Cannot sync git when platform=local",

[nsheaps]

Discovered using LOG_LEVEL=debug ..., I ran into this, and it was caused by having open renovate branches.

When I ran it, my default config doesn't mention rebasing, which makes "rebaseWhen": "conflicted". That results in these log lines in debug:

DEBUG: Converting rebaseWhen=auto to rebaseWhen=conflicted because no rule for behind-base-branch applies (repository=local, branch=renovate/actions-checkout-6.x
)
DEBUG: Branch already exists (repository=local, branch=renovate/actions-checkout-6.x)
DEBUG: Skipping behind base branch check due to rebaseWhen=conflicted (repository=local, branch=renovate/actions-checkout-6.x)
DEBUG: Branch does not need rebasing (repository=local, branch=renovate/actions-checkout-6.x)
DEBUG: Using reuseExistingBranch: true (repository=local, branch=renovate/actions-checkout-6.x)
DEBUG: manager.getUpdatedPackageFiles() reuseExistingBranch=true (repository=local, branch=renovate/actions-checkout-6.x)
 WARN: Error updating branch (repository=local, branch=renovate/actions-checkout-6.x)
       "err": {
         "message": "Cannot sync git when platform=local",
         "stack": "Error: Cannot sync git when platform=local\n 
...

In an attempt to silence these messages on a whim I set --rebaseWhen="never" in the cli options passed for running the dry run.

Doing so silenced the errors, however I still believe this is a bug where --dryRun=full ends up trying to make changes (and the error prevents it, but it shouldn't be trying in the first place)