-
Notifications
You must be signed in to change notification settings - Fork 0
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: reducing time to deploy but limiting build scope #431
chore: reducing time to deploy but limiting build scope #431
Conversation
WalkthroughThe modification focuses on altering the build command within a GitHub Actions workflow. It specifically aims to streamline the build process by excluding certain packages from being built. This exclusion targets packages with names starting with Changes
TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
Bundle Size (components)
Overall bundle size: 79.73 KB (+9 B +0.01%) Bundle Size (form components)
Overall bundle size: 49.22 KB (+5 B +0.01%) Bundle Size (system)
Overall bundle size: 53.19 KB (+270 B +0.50%) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: .coderabbit.yaml
Files selected for processing (1)
- .github/workflows/deploy-pages.yml (1 hunks)
Additional comments: 1
.github/workflows/deploy-pages.yml (1)
- 42-42: The optimization by excluding specific packages (
@versini/example-*
,@versini/documentation
, and@versini/bundlesize
) from the build process is a strategic approach to streamline deployments. However, it's followed by a targeted build command for the@versini/documentation
package. Ensure that this two-step build process indeed contributes to the overall efficiency of the deployment, and consider measuring the deployment time before and after this change to verify its impact.
Summary by CodeRabbit