.gitignore generator

Client

Select stack templates and export a combined .gitignore. Pair with the .env editor for local env files (never commit secrets).

About .gitignore generator

Combine stack templates (Node, Python, Go, IDEs) into a starter .gitignore—copy or download locally. The interactive transform on this page runs in your browser tab—Toolcore does not need your paste for the core operation described above.

How to use this page

Paste or type in the main workspace, run the primary action from the toolbar, then copy or download the result. Use Load example when the page offers it, or URL prefill (?q= / ?qb=) so agents and tickets open the same input.

Templates

?

Check stacks you use, then copy or download. Review before commit—templates are starting points, not a full audit.

Nearby workflows on Toolcore

  • .env / dotenv editor — Edit KEY=value files—sort, dedupe, issues, JSON preview and import; browser-only. for the next text or markup step in your edit loop.
  • Markdown preview — Render Markdown to sanitized HTML in your browser—paste notes or README drafts. for the next text or markup step in your edit loop.
  • String case converter — camelCase, snake_case, kebab-case, PascalCase, CONST_CASE from one paste—client-side. for the next text or markup step in your edit loop.
  • JSON formatter — JSON format online: pretty-print, minify, validate, escape, download . for the next text or markup step in your edit loop.

Common use cases

  • Bootstrap a new repo with sensible ignores before the first commit.
  • Add macOS and IDE cruft rules on top of a language template.
  • Share a starting .gitignore with teammates during project setup.

Common mistakes to avoid

  • Committing without review

    Templates may ignore files you actually need—edit lines before git add.

FAQ

Does this replace github/gitignore?

It covers common stacks in one place; large org-specific rules may still need custom lines.

More tools

Related utilities you can open in another tab—mostly client-side.