Move crash-context to this repo#190
Merged
Merged
Conversation
Jake-Shadle
force-pushed
the
move-crash-context
branch
from
July 15, 2026 09:07
3bcdcda to
323d510
Compare
gabrielesvelto
approved these changes
Jul 15, 2026
gabrielesvelto
left a comment
Contributor
There was a problem hiding this comment.
LGTM. Thanks this will make our lives simpler!
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
2 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.
It makes much more sense for crash-context to live here since it's so closely tied to minidump-writer, in addition to the work of adding a new platform to it requiring work in minidump-writer as well before it is actually useful.