Skip to content

feat: Ignore editor-specific files and folders #2108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rosidae opened this issue Apr 16, 2025 · 3 comments
Open

feat: Ignore editor-specific files and folders #2108

rosidae opened this issue Apr 16, 2025 · 3 comments
Labels
🌟 enhancement New feature or request

Comments

@rosidae
Copy link

rosidae commented Apr 16, 2025

Is your feature request related to a problem? Please describe.

Yes, editor-specific files should not be pushed to a repository by default as they're specific to:

  • The editor being used
  • The user's preferences and opinions

Describe the solution you'd like to see

By default, add the following to .gitignore

  • .cursor
  • .cursorrules
  • .windsurfrules
  • .vscode
  • .idea

Describe alternate solutions

Ask what editor they use, and add the corresponding entries to the .gitignore

Cursor (VS Code fork)

.cursor
.cursorrules
.vscode

Windsurf (VS Code fork)

.windsurfrules
.vscode

VS Code

.vscode

JetBrains-based editor

.idea

Additional information

Expands on #1904

@rosidae rosidae added the 🌟 enhancement New feature or request label Apr 16, 2025
@phaux
Copy link

phaux commented May 6, 2025

I always commit .vscode

@jasmesp
Copy link

jasmesp commented May 7, 2025

I definitely think that, at minimum, anything related to AI model behavior shouldn't be committed by default. I'd be pretty spooked if my AI suddenly switched its "personality" and/or eagerness to run around refactoring, etc. I would feel pretty bad if someone found their IDE's AI assistant swearing at them and making k-pop jokes if I accidentally pushed my rules to a repo.

I always commit .vscode

Do you think it should be default behavior for T3 projects though? I definitely get sharing linting and formatting configs etc, but am unclear on the benefits of sharing editor configs. I'm totally open to the idea that I'm missing something, but I get a little tweaky if my environment changes on me.

@phaux
Copy link

phaux commented May 7, 2025

When I browse repos on github they usually have .vscode in the repo. Even this one does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌟 enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants