Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/aashishtamsya/awesome-gitignore-templates
A curated collection of useful gitignore templates for different programming languages while pushing your code to git. 😊 📝
https://github.com/aashishtamsya/awesome-gitignore-templates
List: awesome-gitignore-templates
Last synced: about 1 month ago
JSON representation
A curated collection of useful gitignore templates for different programming languages while pushing your code to git. 😊 📝
- Host: GitHub
- URL: https://github.com/aashishtamsya/awesome-gitignore-templates
- Owner: aashishtamsya
- License: cc0-1.0
- Created: 2016-07-18T07:47:59.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2017-05-31T07:23:11.000Z (over 7 years ago)
- Last Synced: 2024-05-19T22:36:49.860Z (8 months ago)
- Homepage:
- Size: 31.3 KB
- Stars: 23
- Watchers: 4
- Forks: 5
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
- awesome-ios - awesome-gitignore-templates - A collection of swift, objective-c, android and many more langugages .gitignore templates. (Xcode / Other Xcode)
- awesome-ios-star - awesome-gitignore-templates - A collection of swift, objective-c, android and many more langugages .gitignore templates. (Xcode / Other Xcode)
README
# Awesome Gitignore Templates
[](https://github.com/vsouza/awesome-ios#other-xcode)
[](LICENSE.md)
A curated collection of useful gitignore templates for different programming languages while pushing your code to git. 😊 📝
# Contents
- [Usage](#usage)
- [Contributors](#contributors)
- [General Information](#general-information)
- [Gitignore Pattern Format](#gitignore-pattern-format)
- [Gitignore Files](#gitignore-files)
- [Contribution](#contribution)
- [License](#license)
## Usage
* Create a file in your repository named .gitignore
* Git uses it to determine which files and directories to ignore, before you make a commit.
* A .gitignore file should be committed into your repository, in order to share the ignore rules with any other users that clone the repository.
## Contributors
- Python Gitignore Template : [Sameera S](https://github.com/sam95), [email protected]
- Ruby Gitignore Template : [Sameera S](https://github.com/sam95), [email protected]
## General Information
* [What is `.gitignore` file](https://help.github.com/articles/ignoring-files/)
* [Git - gitignore Documentation](https://git-scm.com/docs/gitignore)
* [How to create a gitignore file](https://help.github.com/articles/ignoring-files/)
## Gitignore Pattern Format
* A blank line matches no files, so it can serve as a separator for readability.
* A line starting with `#` serves as a comment.
* An optional prefix `!` which negates the pattern; any matching file excluded by a previous pattern will become included again. If a negated pattern matches, this will override lower precedence patterns sources.
* If the pattern ends with a slash, it is removed for the purpose of the following description, but it would only find a match with a directory. In other words, `foo/` will match a directory `foo` and paths underneath it, but will not match a regular file or a symbolic link `foo` (this is consistent with the way how pathspec works in general in git).
* If the pattern does not contain a slash `/`, git treats it as a shell glob pattern and checks for a match against the pathname relative to the location of the `.gitignore` file (relative to the toplevel of the work tree if not from a `.gitignore` file).
* Otherwise, git treats the pattern as a shell glob suitable for consumption by fnmatch(3) with the `FNM_PATHNAME` flag: wildcards in the pattern will not match a `/` in the pathname. For example, `Documentation/*.html` matches `Documentation/git.html` but not `Documentation/ppc/ppc.html` or `tools/perf/Documentation/perf.html`.
* A leading slash matches the beginning of the pathname. For example, `/*.c` matches `cat-file.c` but not `mozilla-sha1/sha1.c`.
## Gitignore Files
## Contribution
1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request 😊 😇
## License
[](/LICENSE.md)