Repository navigation
docs(rfc): Add Tango conflict analyzer design - #845
Merged
Merged
Conversation
manjari25
requested review from
a team,
behinddwalls and
sbalabanov
as code owners
October 12, 2026 19:50
sbalabanov
requested changes
Oct 13, 2026
manjari25
force-pushed
the
manjari/tango-conflict-analyzer-rfc
branch
from
October 14, 2026 01:16
8ac91f0 to
746d206
Compare
behinddwalls
approved these changes
Oct 15, 2026
sbalabanov
approved these changes
Oct 15, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Why?
Provides a way to perform conflict analysis rooted in a build graph as opposed to file overlaps or all conflicts.
What?
Adds an RFC for a Tango-backed
conflict.Analyzerthat stores each batch's changed targets as a signature of 64-bit IDs in a durable store with an in-memory cache, and treats batches as conflicting when their signatures share an ID.Test Plan
Docs only change - Implementation to follow.
Issue