awesome-gitignore-templates alternatives and similar libraries
Based on the "Other Xcode" category.
Alternatively, view awesome-gitignore-templates alternatives based on common mentions on social networks and blogs.
9.5 0.0 L5 awesome-gitignore-templates VS SynxA command-line tool that reorganizes your Xcode project folder to match your Xcode groups.
3D Touch shortcuts in the Simulator
Xcode Developer Disk Images is needed when you want to put your build to the device, however sometimes your Xcode is not updated with the latest Disk Images, you could find them here for convenience.
A curated list of useful xcode scripts 📝.
Template for iOS Swift project generation.
Xcode Template of VIPER Module which generates all layers of VIPER.
Xcode Template Manager is a Swift command line tool that helps you manage your Xcode project templates.
This extension ports popular Xcode keyboard shortcuts to Visual Studio Code.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of awesome-gitignore-templates or a related project?
Awesome Gitignore Templates
A curated collection of useful gitignore templates for different programming languages while pushing your code to git. 😊 📝
- General Information
- Gitignore Pattern Format
- Gitignore Files
- 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.
- Python Gitignore Template : Sameera S, [email protected]
- Ruby Gitignore Template : Sameera S, [email protected]
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
fooand 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
.gitignorefile (relative to the toplevel of the work tree if not from a
- Otherwise, git treats the pattern as a shell glob suitable for consumption by fnmatch(3) with the
FNM_PATHNAMEflag: wildcards in the pattern will not match a
/in the pathname. For example,
- A leading slash matches the beginning of the pathname. For example,
- Fork it!
- Create your feature branch:
git checkout -b my-new-feature
- Commit your changes:
git commit -am 'Add some feature'
- Push to the branch:
git push origin my-new-feature
- Submit a pull request 😊 😇
*Note that all licence references and agreements mentioned in the awesome-gitignore-templates README section above are relevant to that project's source code only.