[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-268":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":10,"languages":10,"totalLinesOfCode":10,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":22,"topics":24,"createdAt":10,"pushedAt":10,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":15,"starSnapshotCount":15,"syncStatus":29,"lastSyncTime":30,"discoverSource":31},268,"gitignore","github\u002Fgitignore","github","A collection of useful .gitignore templates","",null,174476,82416,3360,70,0,18,124,540,87,120,"Creative Commons Zero v1.0 Universal",false,"main",[25,5],"git","2026-06-17 04:00:02","# A collection of `.gitignore` templates\n\nThis is GitHub’s collection of [`.gitignore`][man] file templates.\nWe use this list to populate the `.gitignore` template choosers available\nin the GitHub.com interface when creating new repositories and files.\n\nFor more information about how `.gitignore` files work, and how to use them,\nthe following resources are a great place to start:\n\n- The [Ignoring Files chapter][chapter] of the [Pro Git][progit] book.\n- The [Ignoring Files article][help] on the GitHub Help site.\n- The [gitignore(5)][man] manual page.\n\n[man]: https:\u002F\u002Fgit-scm.com\u002Fdocs\u002Fgitignore\n[help]: https:\u002F\u002Fhelp.github.com\u002Farticles\u002Fignoring-files\n[chapter]: https:\u002F\u002Fgit-scm.com\u002Fbook\u002Fen\u002Fv2\u002FGit-Basics-Recording-Changes-to-the-Repository#_ignoring\n[progit]: https:\u002F\u002Fgit-scm.com\u002Fbook\n\n## Folder structure\n\nWe support a collection of templates, organized in this way:\n\n- The root folder contains templates in common use, to help people get started\n  with popular programming languages and technologies. These define a meaningful\n  set of rules to help get started, and ensure you are not committing\n  unimportant files into your repository.\n- [`Global`](.\u002FGlobal) contains templates for various editors, tools and\n  operating systems that can be used in different situations. It is recommended\n  that you either [add these to your global template](https:\u002F\u002Fdocs.github.com\u002Fen\u002Fget-started\u002Fgetting-started-with-git\u002Fignoring-files#configuring-ignored-files-for-all-repositories-on-your-computer)\n  or merge these rules into your project-specific templates if you want to use\n  them permanently.\n- [`community`](.\u002Fcommunity) contains specialized templates for other popular\n  languages, tools, and projects that don't currently belong in the mainstream\n  templates. These should be added to your project-specific templates when you\n  decide to adopt the framework or tool.\n\n## What makes a good template?\n\nFirst and foremost, a template contribution must adhere to our\n[Contributing Guidelines](CONTRIBUTING.md).\n\nA template should contain a set of rules to help Git repositories work with a\nspecific programming language, framework, tool or environment.\n\nIf it's not possible to curate a small set of useful rules for this situation,\nthen the template is not a good fit for this collection.\n\nIf a template is mostly a list of files installed by a particular version of\nsome software (e.g. a PHP framework), it could live under the `community`\ndirectory. See [versioned templates](#versioned-templates) for more details.\n\nIf you have a small set of rules, or want to support a technology that is not\nwidely in use, and still believe this will be helpful to others, please read the\nsection about [specialized templates](#specialized-templates) for more details.\n\nInclude details when opening a pull request if the template is important and visible. We\nmay not accept it immediately, but we can promote it to the root at a later date\nbased on interest.\n\nPlease also understand that we can’t list every tool that ever existed.\nOur aim is to curate a collection of the _most common and helpful_ templates,\nnot to make sure we cover every project possible. If we choose not to\ninclude your language, tool, or project, it’s not because it’s not awesome.\n\n## Contributing guidelines\n\nPlease see our [Contributing Guidelines](CONTRIBUTING.md).\n\n## Versioned templates\n\nSome templates can change greatly between versions, and if you wish to contribute\nto this repository we need to follow this specific flow:\n\n- the template at the root should be the current supported version\n- the template at the root should not have a version in the filename (i.e.\n  \"evergreen\")\n- previous versions of templates should live under `community\u002F`\n- previous versions of the template should embed the version in the filename,\n  for readability\n\nThis helps ensure users get the latest version (because they'll use whatever is\nat the root) but helps maintainers support older versions still in the wild.\n\n## Specialized templates\n\nIf you have a template that you would like to contribute, but it isn't quite\nmainstream, please consider adding this to the `community` directory under a\nfolder that best suits where it belongs.\n\nThe rules in your specialized template should be specific to the framework or\ntool, and any additional templates should be mentioned in a comment in the\nheader of the template.\n\nFor example, this template might live at `community\u002FDotNet\u002FInforCRM.gitignore`:\n\n```gitignore\n# gitignore template for InforCRM (formerly SalesLogix)\n# website: https:\u002F\u002Fwww.infor.com\u002Fproduct-summary\u002Fcx\u002Finfor-crm\u002F\n#\n# Recommended: VisualStudio.gitignore\n\n# Ignore model files that are auto-generated\nModelIndex.xml\nExportedFiles.xml\n\n# Ignore deployment files\n[Mm]odel\u002F[Dd]eployment\n\n# Force include portal SupportFiles\n!Model\u002FPortal\u002F*\u002FSupportFiles\u002F[Bb]in\u002F\n!Model\u002FPortal\u002FPortalTemplates\u002F*\u002FSupportFiles\u002F[Bb]in\n```\n\n## Contributing workflow\n\nHere’s how we suggest you go about proposing a change to this project:\n\n1. [Fork this project][fork] to your account.\n2. [Create a branch][branch] for the change you intend to make.\n3. Make your changes to your fork.\n4. [Send a pull request][pr] from your fork’s branch to our `main` branch.\n\nUsing the web-based interface to make changes is fine too, and will help you\nby automatically forking the project and prompting to send a pull request too.\n\n[fork]: https:\u002F\u002Fhelp.github.com\u002Farticles\u002Ffork-a-repo\u002F\n[branch]: https:\u002F\u002Fhelp.github.com\u002Farticles\u002Fcreating-and-deleting-branches-within-your-repository\n[pr]: https:\u002F\u002Fhelp.github.com\u002Farticles\u002Fusing-pull-requests\u002F\n\n## License\n\n[CC0-1.0](.\u002FLICENSE).\n\n","这是一个收集了大量有用的`.gitignore`模板的项目，旨在帮助开发者避免将不重要的文件提交到Git仓库。其核心功能是提供针对不同编程语言、框架、工具和环境定制的忽略规则集。项目结构清晰，分为常用模板、全局配置模板及社区贡献模板三大类，方便用户根据需要选择合适的模板。适用于各种软件开发场景，特别是当开始一个新的项目或使用新的技术栈时，能够快速配置好版本控制系统中的忽略文件列表，从而提高工作效率。",2,"2026-06-17 02:32:48","top_all"]