What is a .gitignore file?

A .gitignore file tells Git which files and directories to ignore — not track, not stage, not commit. Common examples are node_modules/, __pycache__/, and .env secrets files.

Is this tool 100% private?

Yes. Template selection and .gitignore generation happen entirely in your browser. Nothing is sent to any server. Generic page-view analytics may record the URL you visit, but never which templates you selected.

Can I combine multiple templates?

Yes — select as many templates as you need. The generator deduplicates overlapping patterns and orders sections consistently (OS → IDE → Language → Framework → Build Tool → Other).

How do I use the raw URL with curl?

Use: curl "https://devzone.tools/tools/gitignore-generator/node-react/raw" > .gitignore. Replace node-react with your combination slug. The raw endpoint returns plain text with the correct Content-Type.

How do I ignore a file that is already tracked by Git?

Adding a file to .gitignore does not untrack it if Git already knows about it. Run: git rm --cached to remove it from tracking without deleting the local file. Then commit the removal.

.gitignore for Gradle + Java + JetBrains

.gitignore for Java projects built with Gradle and developed in IntelliJ IDEA.

Quick presets

Selected (3)

GradleJavaJetBrains

Your selections never leave your browser. Generation happens entirely client-side.

Raw

31 patterns · 587 B

# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator
# Templates: JetBrains, Java, Gradle
# 2026-05-28

# ---- JetBrains ----
# JetBrains IDEs
.idea/
*.iws
*.iml
*.ipr
out/
!**/src/main/**/out/
!**/src/test/**/out/
.idea/caches/
.idea/libraries/
.idea/modules/
.idea/modules.xml
.idea/workspace.xml

# ---- Java ----
# Java
*.class
*.log
*.ctxt
.mtj.tmp/
*.jar
*.war
*.nar
*.ear
*.zip
*.tar.gz
*.rar
hs_err_pid*
replay_pid*

# ---- Gradle ----
# Gradle
.gradle/
**/build/
!src/**/build/
!gradle/wrapper/gradle-wrapper.jar
local.properties
*.gradle.kts.~lock~

Why use Gradle + Java + JetBrains together?

The most common modern Java setup: Gradle as the build tool, IntelliJ IDEA as the IDE. This combination layers three templates so nothing slips through.

Gradle contributes .gradle/ caches and build/ output. The Gradle wrapper (gradlew, gradlew.bat, and gradle/wrapper/gradle-wrapper.jar) should always be committed — it ensures every contributor and CI runner uses the same Gradle version without a system install.

The Java template covers compiled .class files plus packaged JAR/WAR/EAR archives. JetBrains adds .idea/ workspace state, *.iml module files, and the out/ build directory IntelliJ creates for non-Gradle runs. Together you get clean, deterministic Gradle/Java repos with no IDE noise.

Related combinations

java-jetbrains java-spring gradle-java

Frequently asked questions

Do I need to commit .gitignore?: Yes — .gitignore should be committed to the repository so all collaborators benefit from the same ignore rules.
How do I add custom patterns?: Open your .gitignore file and add the pattern on a new line. Use # for comments, * for wildcards, / to match directories, and ! to un-ignore a previously ignored path.
How do I ignore a file that is already tracked?: Adding a file to .gitignore does not remove it from tracking if it was previously committed. Run: git rm --cached <file> to stop tracking it without deleting the file locally.
Why combine Gradle and Java and JetBrains?: The most common modern Java setup: Gradle as the build tool, IntelliJ IDEA as the IDE. This combination layers three templates so nothing slips through.

Looking for something else? Browse all templates →