-
Notifications
You must be signed in to change notification settings - Fork 109
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
Introduce .gitattributes
in favor of .distignore
#217
Comments
Will also want to make sure that |
ZIPs created from a release tag contains non required files: Benefits
|
@mitogh Good point, that makes sense to me. So as a summary what needs to be done here:
|
Feature Description
The current release zips created by GH everytime a new tag is created includes files that are not part of the release, for example:
Contains tests and configuration files, non required for testing or usage of the plugin.
The deploy action would use either:
.disignore
.gitattributes
To exclude files that are going to be deployed so we can safely move
.disignore
to.gitattributes
one of the things to consider is when moving the content into.gitattributes
is the fact that the settingexport-ignore
should be added after each file for example:export-ignore
Additional parameters.
The text was updated successfully, but these errors were encountered: