feat: store commit performance data #67
Merged
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
✅ Deploy Preview for rspack-ecosystem-benchmark ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
SyMind
approved these changes
Jun 12, 2025
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.
store performance datat by commit for easy find the donwgrade change commit
usage
then the perf data will store at as below,(e.g. commit id is
15aa411a089296f27dc1422fdba4cedbdf73951b)commits/15/aa411a089296f27dc1422fdba4cedbdf73951b/*.jsonif commit id isn't provided, it will store data in date named dir eg.
2025-01-02/*.json