Configuring workflows for your Flutter projects
Article Summary
Very Good Ventures just open-sourced their internal CI/CD secret weapon for Flutter teams. If you're still writing GitHub Actions from scratch for every project, you're working way too hard.
Very Good Ventures released Very Good Workflows, a collection of reusable GitHub Actions specifically designed for Flutter and Dart projects. The article walks through how to implement these pre-built workflows and customize them for your team's needs.
Key Takeaways
- Two reusable workflows handle Flutter and Dart package quality checks automatically
- Setup takes just 5 lines of YAML per project
- Customize coverage excludes, SDK versions, and working directories via simple inputs
- Path filtering prevents unnecessary builds when only docs change
- Extend workflows with custom jobs like dependency graph visualization
Very Good Workflows eliminates repetitive CI/CD configuration by providing production-ready, customizable GitHub Actions for Flutter and Dart projects.
About This Article
The Flutter and Dart teams at Very Good Ventures kept writing the same GitHub Actions configuration over and over. Every new package meant manually setting up identical workflow steps from scratch.
Very Good Ventures built reusable GitHub workflows using GitHub's reusable workflows feature. Now teams can reference pre-built dart_package and flutter_package workflows with a single uses statement in their YAML configuration.
Teams can now set up complete CI/CD pipelines with customizable inputs for coverage excludes, SDK versions, and working directories. This cuts down on repetitive configuration and lets them use path-based filtering to skip builds when only documentation changes.