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 to stop tracking it without deleting the file locally.

Why does Bazel create symlinks in the project root?

Bazel creates bazel-bin/, bazel-out/, and bazel-testlogs/ as symlinks pointing to the actual output base outside the workspace. These should always be ignored.

.gitignore for Bazel

Bazel build output directories and symlinks.

Quick presets

Selected (1)

Bazel

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

Raw

2 patterns · 157 B

# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator
# Templates: Bazel
# 2026-04-20

# ---- Bazel ----
# Bazel
/bazel-*
/.bazel

What this template ignores

Ignores Bazel symlinks (bazel-bin, bazel-out, bazel-testlogs) created in the workspace root and the .bazel/ cache.

Commonly paired with

java go c cpp Combine →

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 does Bazel create symlinks in the project root?: Bazel creates bazel-bin/, bazel-out/, and bazel-testlogs/ as symlinks pointing to the actual output base outside the workspace. These should always be ignored.

Looking for something else? Browse all templates →