-
Notifications
You must be signed in to change notification settings - Fork 226
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
Can we ignore some files for publishing but include in the repo? #2566
Comments
I think we should have a .pubignore or similar file. |
We already respect Other possible use-case in #2222. I imagine that if you have a |
It seems we can use That would however put a requirement on git - which might be acceptable if we still allow having no .pubignore file. |
External dependencies provided by the system, such as I suppose it works better for |
On the other hand, we can test if |
It is quite well specified: https://git-scm.com/docs/gitignore , but not trivial to implement. Funnily enough we hardly ever get issues around our external dependency on git. I guess there is only one implementation that everybody shares. Most of our tar issues seem to stem from the system tar being different for different systems. |
Is there any plans on supporting .pubignore or ingore: ["", ""] in pubspec? like npm and package.json handles it. |
I don't think it's a high priority for us at the moment. But if someone wants to work on it, I'll be happy to help define the feature, review and land it. Otherwise, please upvote, and mention any novel use-cases you might have. |
I'd like to leave some files in a package's repository on GitHub, but at the same time, make those files excluded when I publish a package on pub.dev.
The issue is that I'd like to add images or gifs to the README so that other developers immediately understand what the package is for. However, I don't want users of my package to have to download these images when they decide to add my package as a dependency.
Can we ignore some files for publishing but include in the repo?
The text was updated successfully, but these errors were encountered: