docs: improve merge confidence api base url variable doc

[mikaello]

Changes

Improved the documentation for the env variable RENOVATE_X_MERGE_CONFIDENCE_API_BASE_URL. I have found it a bit confusing how this works, so I try to document this as I figure it out.

Context

See mend/renovate-ce-ee#488 (comment) for some context.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[HonkingGoose]

Please avoid force-pushing to the PR's branch. This resets the review progress, which makes it harder to see what changed.

We will squash merge this PR, and thus end with one clean commit on the main branch. So you do not need to keep your branch tidy. 🙂

[mikaello]

Please avoid force-pushing to the PR's branch. This resets the review progress, which makes it harder to see what changed.

I see, I will remember this for future contributions.

I think there is a repo setting to disable the rebase button in PRs. Since it was not disabled I thought this was ok to select that option in the drop down menu for updating the branch.

[HonkingGoose]

Thank you for remembering it for future contributions! 😄

Hmm. I think that repository setting only limits the type of merges to the main branch. In short, it limits what merges a maintainer can select when merging a PR.

That repository setting does not seem to change which options the user sees to sync their fork of renovate.

[HonkingGoose]

@mikaello thank you for improving the docs with your PR! ❤️🥳

[renovate-release]

🎉 This PR is included in version 37.327.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 37.327.0

Your semantic-release bot 📦🚀