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(config options): example to limit registryAliases to one manager #30038

Conversation

HonkingGoose
Copy link
Collaborator

Changes

  • Show example of using a top-level manager object to limit the scope of a registryAliases block
  • Add titles to the codeblocks to label each example properly

Context

Quote from #29747 (comment)

I think this issue still needs a fix because:

  • Coming up with this solution is non-trivial
  • The existence of top-level manager objects is not well-documented

I can't fix any code problems, that's for the maintainers. But I can add a example to the docs. 😉

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

@SanOk1989

This comment has been minimized.

1 similar comment
@SanOk1989

This comment has been minimized.

@SanOk1989

This comment has been minimized.

@viceice viceice requested review from rarkins and secustor July 7, 2024 17:16
@secustor secustor added this pull request to the merge queue Jul 14, 2024
Merged via the queue into renovatebot:main with commit 911e211 Jul 14, 2024
38 checks passed
@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 37.431.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

@HonkingGoose HonkingGoose deleted the docs/29747-limiting-registy-alias-to-single-manager branch July 15, 2024 13:48
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 15, 2024
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.

4 participants