.gitignore
Pick languages, frameworks and IDEs, then generate a merged .gitignore ready to download.
Select at least one language, framework, IDE or operating system above to generate the .gitignore.
What a .gitignore is
A .gitignore is a text file, at the root of the repository, that tells Git which files and folders should never be tracked — installed dependencies (node_modules/, venv/), build artifacts (dist/, build/), IDE configuration files (.vscode/, .idea/) and operating-system files (.DS_Store, Thumbs.db). Without it, those files (which have no value outside your machine, and sometimes add up to gigabytes) end up committed alongside your actual source code. This tool assembles the right .gitignore from official templates, combining as many languages/frameworks/IDEs as your project uses.
How combining multiple templates works
Each selected language/framework/IDE/operating system becomes its own section in the final file, with a heading identifying where it came from (### Node ###, ### macOS ###, and so on) — the same format used by reference tools in the market. When two selected sections share the exact same rule line (for example, Node and Angular both listing node_modules/ separately), the line only appears once, in the first section where it showed up — the rest of the file never duplicates a rule that's already present. Comments and blank lines from each template are kept as-is, even when the text repeats across sections (they organize the section they're in, they're not a rule that could 'duplicate').
Where the templates come from
All content comes, with no changes, from the official github/gitignore repository (community-maintained under GitHub's curation — the same source used by gitignore.io) — never written from memory. Templates ship embedded in Nexinon (100% local execution, no network call at all), so a change to the official source only reaches here through a future manual update of the catalog, not automatically. The current catalog covers the most-used languages, frameworks, IDEs and operating systems — it's not a copy of the entire official repository (which has hundreds of files), so a very specific technology might not be on the list yet.
My project already has a .gitignore
This tool generates a new file from scratch — it doesn't read or merge a .gitignore you already have. If your project already has one, the safest way to use the result is to copy just the missing sections (e.g. you already had a Node .gitignore and now want to add the VS Code section) to the end of the existing file, instead of overwriting it with the download — overwriting would discard any custom rule you already added by hand.
Frequently asked questions
Because that's the only name Git recognizes as an ignore file — unlike every other download in the catalog (which carries a date and time in the name), a ".gitignore" with a timestamp in the name would need to be renamed by hand before it worked, defeating the point of downloading a file that's ready to use.
The current catalog covers the most-used technologies, not the entire official repository (github/gitignore has hundreds of templates) — see "Where the templates come from", above. Until a specific technology is added to the catalog, the most direct path is to generate the .gitignore with what's already available and complete it by hand with the missing rules.
Deliberate deduplication — see "How combining multiple templates works", above. When two selected sections have the exact same rule line, it's only written once, in the first section; repeating the same rule multiple times in the file wouldn't change Git's behavior, it would just make the file longer for no reason.
No — templates ship embedded in Nexinon (which is why the tool works 100% offline, with no network call on every generation), so a change to the official repository only reaches here through a future manual catalog update, not in real time.
Not on its own. The Arduino / PlatformIO template covers the ecosystem's own build artifacts (.pio/, temporary compilation files); secrets.h is a project convention, not an ecosystem artifact, so no language/IDE template would know to add that line by itself. For that, use the secrets.h Generator — it generates the example file with placeholders and the exact .gitignore line (secrets.h) that protects it.
Yes, it's just a plain text file — adding, removing or commenting out a line after downloading has no special restriction. The generated file is only the recommended starting point for the chosen combination, not a closed document.
Nexinon Principles
Privacy
Your data never leaves your browser.No account needed
Use it now, no account or password.Free
No usage limits, no paid plan.Trustworthy content
Full explanation behind every tool, not just the result.