-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
fix: bundle
includes ephemeral and ignored files
#781
Comments
Hey @renancaraujo, I hope you're doing well. I am trying to update my brick, but after updating my mason, I am encountering the following error:
I'm not sure if this error is related to this issue, or if I'm missing something in the process. Could you please provide some guidance on how to resolve this issue? Any help would be greatly appreciated. Thank you! |
Hi @jigarfumakiya that means you have default content in the README of your brick. Can you please make sure your brick’s README reflects your custom brick? If you’re still having trouble please provide a link to your brick and I’m happy to take a closer look 👍 Edit: I took a look at your brick and I believe you just need to remove or adjust the “Getting Started” section in your README since that section was autogenerated by mason. |
A change to the readme fixes the problem. @felangel, thank you for responding so quickly. |
@renancaraujo @felangel any updates to this issue? Would having a |
Any updates here? I'm open to contribute with the |
I think supporting a |
Can I get assigned? 🙌 |
the .ignore file is also being copied to the build folder as listed here |
Description
Mason's
bundle
(thereforepublish
too) include files ignored by.gitignore
in the file.This can lead to a handful of situations where local files are shipped within a brick that the user didn't intend to.
For example:
very_good_flutter_plugin
included several files under.dart_tool
and.idea
after runningmason publish
locally. See this diff.Expected Behavior
It is necessary to provide a what to ignore .gitignored files or provide a species of .masonignore file to be placed within
The text was updated successfully, but these errors were encountered: