Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: explain limitation on amount of branches that can be automerged in one run #11890

Merged
merged 2 commits into from Sep 27, 2021

Conversation

HonkingGoose
Copy link
Collaborator

Changes:

Context:

Might be good to put this explanation in the key-concepts/automerge.md page.

If this is not suitable, feel free to close the PR and explain the reasoning. 😉

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/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

docs/usage/key-concepts/automerge.md Outdated Show resolved Hide resolved
docs/usage/key-concepts/automerge.md Outdated Show resolved Hide resolved
Co-authored-by: Rhys Arkins <rhys@arkins.net>
@rarkins rarkins merged commit 54c1ccd into renovatebot:main Sep 27, 2021
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 27.19.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@HonkingGoose HonkingGoose deleted the patch-1 branch September 28, 2021 08:24
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants