ci: use different keys for different projects#743
Conversation
|
<!-- Thank you for submitting a pull request! We appreciate the time and effort you have invested in making these changes. Please ensure that you provide enough information to allow others to review your pull request. Upon submission, your pull request will be automatically assigned with reviewers. If you want to learn more about contributing to this project, please visit: https://github.com/lynx-family/lynx-stack/blob/main/CONTRIBUTING.md. --> ## Summary <!-- Can you explain the reasoning behind implementing this change? What problem or issue does this pull request resolve? --> We accidentally removed "Deploy" and "Test" in #743. :) <!-- It would be helpful if you could provide any relevant context, such as GitHub issues or related discussions. --> ## Checklist <!--- Check and mark with an "x" --> - [ ] Tests updated (or not required). - [ ] Documentation updated (or not required).
Bundle ReportChanges will increase total bundle size by 3.21kB (0.5%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: @lynx-js/example-react-lynx-cjsAssets Changed:
|
CodSpeed Performance ReportMerging #743 will not alter performanceComparing Summary
|
React Example#13 Bundle Size — 233.45KiB (-25.36%).4cae120(current) vs 5c16b9e main#2(baseline) Warning Bundle introduced 2 new packages: @hongzhiyuan/preact, @swc/helpers – View changed packages Bundle metrics
Bundle size by type
Bundle analysis report Branch colinaaa:colin/0509/key Project dashboard Generated by RelativeCI Documentation Report issue |
Summary
We should use different key for different projects in a monorepo.
Checklist