-
Notifications
You must be signed in to change notification settings - Fork 150
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
docs: improve contributing experience when generating bundles #666
base: main
Are you sure you want to change the base?
Conversation
@@ -0,0 +1,16 @@ | |||
#!/bin/bash | |||
# Runs `mason bundle` to generate bundles for all bricks within the top level bricks directory. |
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.
Avoid to generate bundles locally because felangel/mason#781
See #881 |
@alestiago anything blocking this PR? |
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 should now commit locally generated bundles because the mason bundle
doesn't discriminate git ignored files. Resulting on bundles with undesired files, suck as pubspec.lock
and others. See the previously linked mason issue.
I'm happy to close this Pull Request or let it be until mason resolves the issue. Either way I think we should consider updating the CONTRIBUTING.md with:
|
Need to get felangel/mason#1227 in and deployed before going back to this work. |
Status
READY
Description
Changes:
CONTRIBUTING.md
generate_local_bundles.sh
to use the local bricks instead of gitType of Change