Print config without token

[ph-fritsche]

What would you like Renovate to be able to do?

Print resolved config on any machine without GitHub personal access token.

Currently $ renovate --print-config fails with FATAL: You must configure a GitHub personal access token

Did you already have any implementation ideas?

Skip the check for personal access token when --print-config is true.

Workaround

When environment variable LOG_LEVEL is set to debug, the output contains the resolved config as debug information.

[rarkins]

--print-config is for printing the repository config, not the bot config. You never get to the repository config without a token. To view bot config, you must do so with log level.

[ph-fritsche]

--username <string> Username for authentication. Currently Bitbucket only.
Tried it anyway. No effect. :(

[rarkins]

I use it in config.js when running using app tokens (which also can't access /user)

[ph-fritsche]

Tried per config file. Same result. initPlatform() also requires gitAuthor to be set. Then it does skip accessing /user.
But then comes the access on POST https://api.github.com/graphql. That fails with 401 Unauthorized of course.
And omitting the token leads back to the starting point.

On second thought I guess a dry run without a user token would fail due to access rate limits anyway.

[ph-fritsche]

So here's an update:
I've set up a workflow running renovate --dry-run on both the base and head of a PR and committing the logs so that one can view the diff.
Have a look at one of the logs here.

That is a step forward in providing information about how a change to the config would alter the expected changes when running renovate.

The provided information about the combined config looks good to me. This should give any maintainer more confidence than resolving it manually.

The dry run log about the PRs to be generated and the updated dependencies is a lot easier to grasp with the diff highlighted.
But there is still room for improvement.

I think the dry run log should contain INFO about the changes that will be proposed in the PRs.
The DRY-RUN: Would commit files to branch renovate/... should be extended by information like newVersion and newValue (as provided for PHP packages under DEBUG: packageFiles with updates) and the commit message.
Maybe the diff of the proposed commits could be logged on INFO level. This way the output would be similar for the different managers and one could change the log_level to reduce the noise.

What do you think?

[rarkins]

I'm fine with enhancements to the dry-run verboseness