Skip to content

chore: untrack .vscode and add it to .gitignore - #87

Merged
pannoury merged 1 commit into
mainfrom
chore/untrack-vscode
Aug 22, 2026
Merged

chore: untrack .vscode and add it to .gitignore#87
pannoury merged 1 commit into
mainfrom
chore/untrack-vscode

Conversation

@pannoury

Copy link
Copy Markdown
Member

.vscode/settings.json was tracked, carrying personal editor preferences — a pipenv env-manager choice and Pylance analysis settings — that every contributor's editor would fight over. Nothing in the build, tests or CI reads it.

The .gitignore already shipped a commented-out .vscode/ entry from the GitHub Python template; this uncomments it so the directory stays out from now on.

Existing clones keep their local .vscode/ — untracking does not delete it for anyone.

.vscode/settings.json carried personal editor preferences - a pipenv
env manager choice and Pylance analysis settings - that every
contributor's editor would fight over. Nothing in the build, tests or
CI reads it.

The .gitignore already shipped a commented-out .vscode/ entry from the
GitHub Python template; this uncomments it so the directory stays out
from now on.
@pannoury
pannoury merged commit a19cbec into main Aug 22, 2026
4 checks passed
@pannoury
pannoury deleted the chore/untrack-vscode branch August 22, 2026 12:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant