NotificationsYou must be signed in to change notification settings
Fork7.7k
Star15.1k

fix(ci): Process only needed files in publish sizes#11439

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

me-no-dev merged 1 commit intomasterfromci/fix-sizes-report

Jun 10, 2025

Merged

fix(ci): Process only needed files in publish sizes#11439

me-no-dev merged 1 commit intomasterfromci/fix-sizes-report

Jun 10, 2025

Conversation

Copy link

Member

P-R-O-C-H-Y commentedJun 5, 2025•
edited
Loading

Description of Change

This pull request includes a refinement to the artifact processing logic in thepublishsizes.yml fixing this workflow. The changes ensure that only specific artifacts (pr_number andpr_cli_compile_*) are processed.

Tests scenarios

Related links

fix(ci): Process only needed files in publish sizes

1fc5f69

P-R-O-C-H-Y self-assigned this

Jun 5, 2025

P-R-O-C-H-Y added the Type: CI & TestingRelated to continuous integration, automated testing, or test infrastructure. label

Jun 5, 2025

P-R-O-C-H-Y requested a review fromlucasssvaz as acode owner

June 5, 2025 13:40

Copy link

Contributor

github-actionsbot commentedJun 5, 2025•
edited
Loading

	Messages
📖	🎉 Good Job! All checks are passing!

👋Hello P-R-O-C-H-Y, we appreciate your contribution to this project!

📘 Please review the project'sContributions Guide for key guidelines on code, documentation, testing, and more.

🖊️ Please also make sure you haveread and signed theContributor License Agreement for this project.

Click to see more instructions ...

This automated output is generated by thePR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with eachpush event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger isnot a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manuallyretry these Danger checks, please navigate to theActions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫dangerJS against1fc5f69