-
Notifications
You must be signed in to change notification settings - Fork 608
ci: Build extensions in one job #5722
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
Conversation
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.
We've reviewed this pull request using the Sourcery rules engine
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.
Pull Request Overview
This PR consolidates the building of Flet extension packages from multiple parallel jobs into a single sequential job to simplify the CI workflow.
- Removed the matrix strategy that built each extension in a separate job
- Combined all extension processing into a loop within one job step
- Updated artifact naming from individual packages to a single combined artifact
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Deploying flet-docs with
|
| Latest commit: |
292c757
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://17f9afa0.flet-docs.pages.dev |
| Branch Preview URL: | https://improve-ci.flet-docs.pages.dev |
Summary by Sourcery
Streamline the CI workflow by consolidating Flet extension builds into a single job, merging Flutter analysis and Python packaging steps, and refining the publish and artifact upload configurations.
CI: