Gitignore Generator
Create a .gitignore file for your programming language or framework.
Select Technologies
.gitignore Output
About the Gitignore Generator
The Gitignore Generator assembles a .gitignore file from the technologies you select. Pick your language and editor, and it writes the patterns that keep build output, dependencies and local settings out of version control.
A .gitignore lists the paths git should pretend do not exist. Without one you end up committing node_modules, compiled files, editor folders and your own secrets, which bloats the repository and leaks information. The file belongs at the repository root.
One thing it cannot do is untrack files that are already committed. Adding a path to .gitignore only affects files git is not yet following, so anything already tracked needs git rm --cached first, and a commit to record the removal.
Common questions about gitignore Generator
What is a .gitignore file?
A list of patterns telling git which files and folders to leave out of version control.
Will it untrack files I already committed?
No. It only affects untracked files. Run git rm --cached path for anything already tracked, then commit.
Where does the file go?
At the repository root, named exactly .gitignore, with the leading dot.
Can I combine several technologies?
Yes. Select every language and tool you use and the patterns are merged into one file.
Can I have more than one .gitignore?
Yes. Git reads one per directory, and patterns in a deeper file apply to that subtree.
What about secrets like API keys?
Ignore the .env file and never commit keys. Ignoring a file that is already tracked does not remove it from history.