Discofork
Repository brief

github/gitignore

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T10:28:59.302Z
3mo ago

github/gitignore

github/gitignore is GitHub’s curated collection of .gitignore templates for common languages, frameworks, tools, editors, and operating systems. It is large, actively maintained, highly forked, and mainly useful as a source for reusable ignore rules rather than as an application or library.

GitHub
Loading tags...
Stars173,214
Forks82,714
Default branchmain
Last pushed2026-02-12T17:50:51Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

20 of 20 fork briefs
Selected

Prefer upstream for nearly everyone. Use this fork only if you specifically need the old PhoneGap template and do not care about the many years of upstream template updates.

Prefer upstream unless you specifically need this fork’s older Visual Studio ignore rules. The fork’s value is narrow and legacy-oriented; its main drawback is that it is far behind current GitHub/gitignore maintenance.

Prefer upstream unless you intentionally want an old, frozen snapshot. This fork offers no added capabilities and is materially out of date.

Prefer upstream unless you specifically need a frozen 2021-era snapshot; this fork offers no visible enhancements and is materially outdated.

Prefer upstream unless you specifically need this repository's old 2014 snapshot. For any current project, the fork is too stale to trust as a source of modern .gitignore templates.

Prefer upstream unless you specifically need the old R and Eclipse tweaks or want a frozen historical snapshot. For most adopters, this fork is too stale to be a practical replacement.

Prefer upstream unless you specifically want a frozen historical copy; this fork appears stale, with no visible fork-specific features and a large gap behind current GitHub/gitignore.

Prefer upstream for nearly all use cases. Choose this fork only if you specifically want an unmodified, stale snapshot to own and maintain yourself.

Prefer upstream unless you specifically need a historical snapshot; this fork adds no visible functionality and is too stale for practical adoption.

Choose upstream unless you specifically need an old frozen copy; this fork offers no visible improvements and is materially behind on template coverage and maintenance.

Prefer upstream unless you specifically need the `DotNet` rename; this fork adds almost nothing else and is far too stale for general adoption.

Do not adopt this fork for normal .gitignore use. Prefer upstream unless you explicitly want a frozen historical copy; this fork adds no capabilities and is far behind on maintenance and templates.

Prefer upstream for almost any new project. Choose this fork only if you specifically want the single Objective-C/Xcode tweak it adds and do not care about receiving current template updates.

Choose this fork only if you want the notebook workflow it adds. If your goal is reusable `.gitignore` templates, upstream is vastly better maintained and far more complete.

Most adopters should prefer upstream. This fork does not add capabilities and is materially outdated, so it is only sensible as a historical archive.

Prefer upstream unless you explicitly want an old frozen snapshot. This fork does not add functionality, and its main tradeoff is losing recent template updates.

Prefer upstream unless you explicitly want an old frozen snapshot. This fork adds nothing new and is materially behind on template maintenance, so it is a poor choice for teams that want current `.gitignore` coverage.

Prefer upstream unless you explicitly need a frozen 2022-era snapshot; this fork offers no visible advantages and is materially stale.

Prefer upstream unless you specifically need an old, frozen copy. This fork offers no visible enhancements and is far behind the active template set, so it is a weak choice for new or actively maintained repositories.

Prefer upstream unless you specifically need an old static snapshot; this fork offers no visible functional advantage and is far behind current templates.