# A collection of `.gitignore` templates
This is GitHub’s collection of [`.gitignore`][man] file templates.
We use this list to populate the `.gitignore` template choosers available
in the GitHub.com interface when creating new repositories and files.
For more information about how `.gitignore` files work, and how to use them,
the following resources are a great place to start:
- The [Ignoring Files chapter][chapter] of the [Pro Git][progit] book.
- The [Ignoring Files article][help] on the GitHub Help site.
- The [gitignore(5)][man] manual page.
[man]: http://git-scm.com/docs/gitignore
[help]: https://help.github.com/articles/ignoring-files
[chapter]: https://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository#_ignoring
[progit]: http://git-scm.com/book
## Folder structure
We support a collection of templates, organized in this way:
- The root folder contains templates in common use, to help people get started
with popular programming languages and technologies. These define a meaningful
set of rules to help get started, and ensure you are not committing
unimportant files into your repository.
- [`Global`](./Global) contains templates for various editors, tools and
operating systems that can be used in different situations. It is recommended
that you either [add these to your global template](https://docs.github.com/en/get-started/getting-started-with-git/ignoring-files#configuring-ignored-files-for-all-repositories-on-your-computer)
or merge these rules into your project-specific templates if you want to use
them permanently.
- [`community`](./community) contains specialized templates for other popular
languages, tools and project, which don't currently belong in the mainstream
templates. These should be added to your project-specific templates when you
decide to adopt the framework or tool.
## What makes a good template?
A template should contain a set of rules to help Git repositories work with a
specific programming language, framework, tool or environment.
If it's not possible to curate a small set of useful rules for this situation,
then the template is not a good fit for this collection.
If a template is mostly a list of files installed by a particular version of
some software (e.g. a PHP framework), it could live under the `community`
directory. See [versioned templates](#versioned-templates) for more details.
If you have a small set of rules, or want to support a technology that is not
widely in use, and still believe this will be helpful to others, please read the
section about [specialized templates](#specialized-templates) for more details.
Include details when opening pull request if the template is important and visible. We
may not accept it immediately, but we can promote it to the root at a later date
based on interest.
Please also understand that we can’t list every tool that ever existed.
Our aim is to curate a collection of the _most common and helpful_ templates,
not to make sure we cover every project possible. If we choose not to
include your language, tool, or project, it’s not because it’s not awesome.
## Contributing guidelines
We’d love for you to help us improve this project. To help us keep this collection
high quality, we request that contributions adhere to the following guidelines.
- **Provide a link to the application or project’s homepage**. Unless it’s
extremely popular, there’s a chance the maintainers don’t know about or use
the language, framework, editor, app, or project your change applies to.
- **Provide links to documentation** supporting the change you’re making.
Current, canonical documentation mentioning the files being ignored is best.
If documentation isn’t available to support your change, do the best you can
to explain what the files being ignored are for.
- **Explain why you’re making a change**. Even if it seems self-evident, please
take a sentence or two to tell us why your change or addition should happen.
It’s especially helpful to articulate why this change applies to _everyone_
who works with the applicable technology, rather than just you or your team.
- **Please consider the scope of your change**. If your change is specific to a
certain language or framework, then make sure the change is made to the
template for that language or framework, rather than to the template for an
editor, tool, or operating system.
- **Please only modify _one template_ per pull request**. This helps keep pull
requests and feedback focused on a specific project or technology.
In general, the more you can do to help us understand the change you’re making,
the more likely we’ll be to accept your contribution quickly.
## Versioned templates
Some templates can change greatly between versions, and if you wish to contribute
to this repository we need to follow this specific flow:
- the template at the root should be the current supported version
- the template at the root should not have a version in the filename (i.e.
"evergreen")
- previous versions of templates should live under `community/`
- previous versions of the template should embed the version in the filename,
for readability
This helps ensure users get the latest version (because they'll use whatever is
at the root) but helps maintainers support older versions still in the wild.
## Specialized templates
If you have a template that you would like to contribute, but it isn't quite
mainstream, please consider adding this to the `community` directory under a
folder that best suits where it belongs.
The rules in your specialized template should be specific to the framework or
tool, and any additional templates should be mentioned in a comment in the
header of the template.
For example, this template might live at `community/DotNet/InforCRM.gitignore`:
```
# gitignore template for InforCRM (formerly SalesLogix)
# website: https://www.infor.com/product-summary/cx/infor-crm/
#
# Recommended: VisualStudio.gitignore
# Ignore model files that are auto-generated
ModelIndex.xml
ExportedFiles.xml
# Ignore deployment files
[Mm]odel/[Dd]eployment
# Force include portal SupportFiles
!Model/Portal/*/SupportFiles/[Bb]in/
!Model/Portal/PortalTemplates/*/SupportFiles/[Bb]in
```
## Contributing workflow
Here’s how we suggest you go about proposing a change to this project:
1. [Fork this project][fork] to your account.
2. [Create a branch][branch] for the change you intend to make.
3. Make your changes to your fork.
4. [Send a pull request][pr] from your fork’s branch to our `main` branch.
Using the web-based interface to make changes is fine too, and will help you
by automatically forking the project and prompting to send a pull request too.
[fork]: https://help.github.com/articles/fork-a-repo/
[branch]: https://help.github.com/articles/creating-and-deleting-branches-within-your-repository
[pr]: https://help.github.com/articles/using-pull-requests/
## License
[CC0-1.0](./LICENSE).
没有合适的资源?快使用搜索试试~ 我知道了~
温馨提示
很多朋友在国内都无法打开https://desktop.github.com/,所以老吕把它的macOS版本放到CSDN里面跟大家分享。 GitHub Desktop是由GitHub开发的完全免费且开源的可自定义的基于Electron的Git客户端应用程序,它允许你与GitHub和其他Git平台(包括Bitbucket和GitLab)进行交互。 它的特点包括漂亮的分区方法,可以轻松地检查带有pull请求的分支,你可以检查图片和代码区块之间的差异,甚至可以使用拖拽的方式从应用程序中添加项目进行管理。 GitHub Desktop 是一种开源工具,可帮助您提高工作效率。 GitHub Desktop 鼓励您和您的团队使用最佳实践协作处理 Git 和 GitHub。 您可以使用 GitHub Desktop 执行许多任务,包括: 以交互方式将更改添加到提交中 快速将合作作者提交到提交中 检出具有拉取请求的分支并查看 CI 状态 比较更改的图像
资源推荐
资源详情
资源评论
收起资源包目录
GitHub Desktop(macOS版)是由GitHub开发的完全免费且开源的基于Electron的Git客户端应用程序 (2000个子文件)
araxis 515B
bc 584B
v8_context_snapshot.x86_64.bin 582KB
._v8_context_snapshot.x86_64.bin 10KB
chrome_crashpad_handler 1MB
codecompare 510B
CodeResources 381KB
CodeResources 24KB
CodeResources 3KB
CodeResources 2KB
CodeResources 2KB
CodeResources 2KB
CodeResources 2KB
CodeResources 2KB
CodeResources 2KB
CodeResources 2KB
renderer.css 299KB
crash.css 20KB
markdown.css 9KB
Current 1B
Current 1B
Current 1B
Current 1B
icudtl.dat 10.14MB
._icudtl.dat 10KB
deltawalker 818B
description 73B
diffmerge 460B
diffuse 395B
libGLESv2.dylib 7.58MB
libvk_swiftshader.dylib 4.28MB
libffmpeg.dylib 2.49MB
libEGL.dylib 220KB
ecmerge 453B
Electron Framework 148.5MB
Electron Framework 35B
emerge 535B
examdiff 493B
exclude 240B
git 3.21MB
git 3.21MB
git-add 3B
git-add--interactive 100B
git-am 3B
git-annotate 3B
git-apply 3B
git-archimport 100B
git-archive 3B
git-bisect 2KB
git-bisect--helper 3B
git-blame 3B
git-branch 3B
git-bugreport 3B
git-bundle 3B
git-cat-file 3B
git-check-attr 3B
git-check-ignore 3B
git-check-mailmap 3B
git-check-ref-format 3B
git-checkout 3B
git-checkout--worker 3B
git-checkout-index 3B
git-cherry 3B
git-cherry-pick 3B
git-clean 3B
git-clone 3B
git-column 3B
git-commit 3B
git-commit-graph 3B
git-commit-tree 3B
git-config 3B
git-count-objects 3B
git-credential 3B
git-credential-cache 3B
git-credential-cache--daemon 3B
git-credential-store 3B
git-cvsexportcommit 100B
git-cvsimport 100B
git-cvsserver 100B
git-daemon 1.83MB
git-describe 3B
git-diagnose 3B
git-diff 3B
git-diff-files 3B
git-diff-index 3B
git-diff-tree 3B
git-difftool 3B
git-difftool--helper 2KB
git-env--helper 3B
git-fast-export 3B
git-fast-import 3B
git-fetch 3B
git-fetch-pack 3B
git-filter-branch 15KB
git-fmt-merge-msg 3B
git-for-each-ref 3B
git-for-each-repo 3B
git-format-patch 3B
git-fsck 3B
git-fsck-objects 3B
共 2000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 20
资源评论
Python老吕
- 粉丝: 12w+
- 资源: 28
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- 金山毒霸1999年最老版
- BLE蓝牙单片机CC2540、CC2541带OSAL操作系统的例程-点亮LED灯.zip
- BLE蓝牙单片机CC2540、CC2541带OSAL操作系统的例程-LED闪烁.zip
- xxs靶机,放入vm中使用
- BLE蓝牙单片机CC2540、CC2541带OSAL操作系统的例程-LED跑马灯.zip
- BLE蓝牙单片机CC2540、CC2541裸机简易C语言程序开发之系统睡眠唤醒-中断唤醒.zip
- BLE蓝牙单片机CC2540、CC2541裸机简易C语言程序开发之系统睡眠唤醒-定时器唤醒.zip
- BLE蓝牙单片机CC2540、CC2541裸机简易C语言程序开发之温湿度传感器DHT11.zip
- BLE蓝牙单片机CC2540、CC2541裸机简易C语言程序开发之温度传感器DS18B20.zip
- 机器学习预处理-表格数据的空值处理-py工程
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功