Skip to content
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

Open
mitogh opened this issue Mar 7, 2022 · 0 comments
Open

Introduce .gitattributes in favor of .distignore #217

mitogh opened this issue Mar 7, 2022 · 0 comments

Comments

@mitogh
Copy link
Member

@mitogh mitogh commented Mar 7, 2022

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.

2022-03-07_16-43

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 setting export-ignore should be added after each file for example:

/.git export-ignore
/node_modules export-ignore

export-ignore

Files and directories with the attribute export-ignore won’t be added to archive files.

Additional parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant