Stop exporting development files

[szepeviktor]

Exclude these files from GitHub ZIP-s and everywhere where those ZIP-s are linked.

Test: git archive HEAD | tar --list

[szepeviktor]

@AnthonyLedesma Could you lend me a click here?

[AnthonyLedesma]

@szepeviktor I am not convinced this is what we need for our workflow. We are integrated with GitHub actions right now, the specific workflow can be seen here:

go/.github/workflows/create-release.yml

Line 103 in 37551b6

gh release create $RELEASE_VERSION -n "${{ github.event.milestone.description }}" -t "$RELEASE_VERSION"

For that specific line, we are using the CLI from cli.github.com to package a release within the pipeline. When testing out our existing flow, with the new .gitattributes file, I get the same results as without the new file. Is possible that the command may need to be modified as well perhaps to pass in a config file, but I am not sure about that.

@EvanHerman Getting a look at what is packaged by this command:

There are some extra files like the config, readme, and lock file. Do you think we should consider changing this release command?

[szepeviktor]

AFAIK gh release create does not package anything.
Releases may have attachments

• "Source.tar.gz" with the very same content as the repo
• And custom attachments

This PR is for GitHub ZIP-s used by Packagist (Composer's repo) and NPM.

[szepeviktor]

When that custom attachment (artifact) is created rsync --include-from=.distinclude a custom list of included files is read, totally unrelated to git.

That artifact is built, thus contains downloaded and generated files.
This PR is related to git, so the development version.
Try git archive HEAD | tar --list with and without this PR. (.gitattributes needs to be committed)

You may ask: Does anyone use Go's development version?