docs: master branch -> main branch, default branch -> base branch

[HonkingGoose]

Changes:

• Replace the term master with main where possible and supported
• Make a section explaining the master vs main branch thing in the FAQ
• Use the term "base branch" instead of "default branch"
• Fix-up some other small stuff I found while doing this PR

Context:

Closes #9693.

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 tick one)

I have verified these changes via:

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

[HonkingGoose]

Some questions from my end. 😉

[rarkins]

I think all platforms support arbitrary domain names. It was always possible to change the default branch of a repo. Let's assume as much.

[viceice]

Yeah, let's speak about default branch where possible and use main and / or master as some examples

[HonkingGoose]

I think all platforms support arbitrary domain names. It was always possible to change the default branch of a repo. Let's assume as much.

Okay!

Yeah, let's speak about default branch where possible and use main and / or master as some examples

All of our code examples now use main instead of master. Or do you want me to use default-branch as the branchname in our config examples?

[viceice]

🤔 i think using default branch is more future prove.

@rarkins what do you think?

[rarkins]

🤔 i think using default branch is more future prove.

@rarkins what do you think?

You're probably right. Although now I look, I think many of these should be "the base branch" instead.

[viceice]

Yeah, base branch is probably a better terminology for renovate

[HonkingGoose]

If we want to be consistent throughout, I would need to find/replace default branch -> base branch throughout the docs in most places. I left those changes out for now, until I know if you like this direction or not. 😄

[viceice]

Sounds good

[HonkingGoose]

I think this is ready for another round of review. 😄

I've changed the pull request title as the scope of the PR has changed between opening and now, please check if that's good. Feel free to change it into something else if needed. 😉

[HonkingGoose]

@rarkins said earlier:

You're probably right. Although now I look, I think many of these should be "the base branch" instead.

I made the change to base branch but I think you're not really happy with that, as most of your suggestions reverted that change. 😄

Can you explain why you didn't like base branch after all? Is it maybe because we also have a baseBranches property that people could get confused with?

[rarkins]

Base branch is a relative term, different to default branch.

A repo has only one default branch (eg main/master) but base branch is relative to PRs and there can be multiple.

To a PR, it's the base branch that matters. To a repo, it's default branch.

[HonkingGoose]

To a PR, it's the base branch that matters. To a repo, it's default branch.

Ah okay! 😄

[renovate-release]

🎉 This PR is included in version 25.8.0 🎉

The release is available on:

• GitHub release
• 25.8.0

Your semantic-release bot 📦🚀