Setup Mono Repo Using Melos #327
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add melos.yaml for project configuration - Add root pubspec.yaml with dev dependencies - Update flutter_bloc dependency in shop_app_example - Add talker_logger dependency overrides in various pubspec_overrides.yaml files
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #327 +/- ##
=======================================
Coverage 98.42% 98.42%
=======================================
Files 28 29 +1
Lines 572 573 +1
=======================================
+ Hits 563 564 +1
Misses 9 9
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…ation - Remove utility shell scripts for deployment, testing, and package management - Add new Melos scripts for test running and shop app example deployment - Simplify project maintenance by centralizing scripts in melos.yaml
- Set up matrix build strategy for multiple packages
chore: Add GitHub Actions workflows for Talker packages
- Change workflow trigger branches from "main" to "master"
- Add test configurations for additional Talker packages - Include talker, talker_bloc_logger, talker_dio_logger, talker_http_logger, talker_logger, and talker_riverpod_logger - Maintain existing configuration for talker_flutter package
- Simplify Flutter setup by removing explicit channel specification - Remove pub dependencies cache step - Add Melos bootstrap command to prepare workspace - Streamline dependency installation process
- Remove deprecated v1 workflows for individual Talker packages - Update GitHub Pages workflow to scope Melos bootstrap to shop_app_example - Remove pull request triggers from GitHub Pages workflow
- Add root-level analysis_options.yaml with recommended lints - Remove redundant analysis_options.yaml files from individual packages and examples - Standardize static analysis configuration across the project
- Update constructor syntax across multiple packages using super parameters - Replace deprecated `Key? key` pattern with `super.key` - Simplify constructor initializations in Talker packages - Remove redundant library declarations and update library syntax - Minor code style improvements and linting adjustments
Contributor
Author
|
@Frezyx Hi, Please let me know if this idea doesn’t work for you, and I’ll close this PR. I spent a few hours working on it, so I just wanted to check again. Thanks! |
Owner
|
Hello @ProjectAJ14 ! |
Frezyx
added
enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @Frezyx,
I wanted to fix an issue but noticed that a lot of things are being handled manually. Since I have been using Melos for a few years now, I found it helpful when dealing with multi-package repositories or monorepos.
I have added Melos setup to this repository.
Now, you can version your package at once using:
Note: I recommend using convention commits. Refer Automated Releases
And publish all packages at once using:
Reference Melos Documentation
Utils Alternatives with Melos Commands
deploy_web.shmelos deploy-shop-app-examplepub_clean_all.shmelos cleanpub_get_all.shmelos bspub_get_all_offline.shmelos bs --offlinepublish_all.shmelos publishtest.shmelos testImproving the Workflow
I saw that there were multiple workflows for the package, so I removed them and replaced them with a single workflow using a matrix strategy. This way, we run the same checks but in less time and with fewer resources.
Bonus: I also added a new workflow that automatically hosts the
examples/shop_app_exampleon GitHub Pages whenever there is a push to the master branch.Take a look—I hope this helps! 🚀