godotengine / godotengine/godot

`.gitignore` written by the editor's Version Control Metadata functionality is incomplete

Open
#93,026 2 comments 0 reactions 0 assignees View on GitHub
discussion topic:codestyle topic:editor
Dominant language
C++
Stars
117k
Forks
26.8k
PR merge metrics
PR metrics pending

Description

### Tested versions

- Reproducible in v4.2.2

### System information

Windows 10.0.19045 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1650 SUPER (NVIDIA; 31.0.15.5152) - Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (8 Threads)

### Issue description

.gitignore doesn't include the same number of files that the official gitignore repository has. For comparison, creating a project with Version Control Metadata set to Git will contain the following .gitignore:

```gitignore
# Godot 4+ specific ignores
godot/
```

Meanwhile, the official Godot .gitignore [found here](https://github.com/github/gitignore/blob/main/Godot.gitignore) is:

```gitignore
# Godot 4+ specific ignores
.godot/

# Godot-specific ignores
.import/
export.cfg
export_presets.cfg

# Imported translations (automatically generated from CSV files)
*.translation

# Mono-specific ignores
.mono/
data_*/
mono_crash.*.json
```

Note that the above quote is strangely formatted due to GitHub. Please click the link above to see what it should actually look like.

The official one should be the one created with Godot.

### Steps to reproduce

1. Create a new project with the Godot Project Manager
2. Set Version Control Metadata to Git

### Minimal reproduction project (MRP)

Not necessary. Any project created with version control metadata set to Git will contain the incomplete .gitignore file.

Contributor guide

Open the contributing guide

Research direction

Start in the Godot Project Manager flow that handles Version Control Metadata set to Git, then locate the generated `.gitignore` content. Compare it with the linked official Godot gitignore and update the generated entries; create a new project with Git metadata to verify the file is complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
godot
Domain
developer-experience
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.