Skip to content

Introduce .gitattributes in favor of .distignore #217

@mitogh

Description

@mitogh

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Good First IssueIssue particularly suitable to be worked on by new contributorsInfrastructureIssues for the overall performance plugin infrastructure

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions