8000 Begin ignoring `.vscode` by liam923 · Pull Request #4186 · oxcaml/oxcaml · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Begin ignoring .vscode #4186

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
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

liam923
Copy link
Contributor
@liam923 liam923 commented Jun 24, 2025

Having .vscode checked into the repo causes tons of headaches for me. I use a switch that isn't named 4.14.1, so I need to have a different .vscode/settings.json. I also make extensive use of vscode tasks, so my tasks.json doesn't match either (in fact, the existing tasks.json is syntactically invalid). To deal with this, I have a number of weird git settings configured. And even still, I often need to run some special scripts when performing various.

I'm sympathetic to the git clean -Xdf issue, but I think there's a managable workaround to it. The below command will do the desired thing.

mv .vscode .vscode-temp && git clean -Xdf && mv .vscode-temp .vscode

This of course could be aliased in a .bashrc, or also aliased via git aliases so that they can be invoked by a command like git my-clean:

git config --global alias.my-clean '!mv .vscode .vscode-temp && git clean -Xdf && mv .vscode-temp .vscode'

@liam923 liam923 requested a review from mshinwell June 24, 2025 20:55
@mshinwell
Copy link
Collaborator

What is the official way of handling per-user settings for repos like this? We can't be the only ones having this problem.

@liam923
Copy link
Contributor Author
liam923 commented Jun 25, 2025

What is the official way of handling per-user settings for repos like this? We can't be the only ones having this problem.

I don't think there's an "official" way. There's not much of a consensus on the internet besides "check .vscode into the repo if you want to share settings", but I can't seem to find any threads where people are sad about the git clean -Xdf issue. Presumably not a lot of people are using git clean -Xdf to clear build artifacts?

@goldfirere
Copy link
Collaborator

I don't yet use VSCode (though I expect to start at some point soonish). But I do use git clean -Xdf many times per day. I don't know if that data point matters.

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.

3 participants
0