Skip to content

Repositories: Guideline for .gitattributes #12

Description

@andreashaerter

We often provide smaller tools and plugins where automatically release-tarballs are more then enough. When creating a release, Github creates a zip and a tar archive (the so called zipball and tarball), you can also get them via specific URLs:

https://api.github.com/repos/<user|org>/<repo>/tarball
https://api.github.com/repos/<user|org>/<repo>/zipball
https://api.github.com/repos/<user|org>/<repo>/tarball/<tag>
https://api.github.com/repos/<user|org>/<repo>/zipball/<tag>

However, these archives contain all files found in the projects repository. To exclude repository content (e.g. documentation, .git-files and so one) from being added to these archives, export-ignore can be used as the release feature pays attention to .gitattributes

Therefore, a useful template for .gitattributes would be as useful als it is for .gitignore

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions