Add alibaba traces as submodule - #5
Merged
Merged
Conversation
Turquoise-T
approved these changes
Feb 4, 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
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.
Summary
Added the Alibaba trace repository as a Git submodule at the top-level directory so that both Gavel and FGD can use it for replication.
Background / Context
Both Gavel and FGD require Alibaba traces for replication. Instead of copying trace data into each project separately, I added the Alibaba trace repository as a Git submodule at the root level to enable shared usage.
Although FGD currently uses only the 2023 trace, there is a possibility that additional Alibaba traces will be used as the project evolves. Therefore, This PR make the entire Alibaba trace repository as a submodule to support future extensibility.
Changes