Adding a short doc on Bingo and how to update build deps with it #4526
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mrWinston
requested review from
bennerv,
cadenmarchese,
hawkowl,
hlipsig,
jharrington22,
kimorris27,
mociarain,
pepedocs,
rogbas,
sankur-codes,
tiguelu,
tsatam,
wanghaoran1988 and
yjst2012
as code owners
mociarain
previously approved these changes
Dec 16, 2025
mrWinston
force-pushed
the
add-short-bingo-doc
branch
from
cab5166 to
3be0b20
Compare
Collaborator
Author
|
/azp run ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Thanks for the addition Marius, the doc LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR adds a brief intro to
bingoand what we're using it for, as well as what we need to do to update build dependencies managed by it.Test plan for issue:
Is there any documentation that needs to be updated for this PR?
How do you know this will function as expected in production?