🔥 Remove IDE-specific configurations and prevent future commits #3074
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm fine with this, if you extend the .editorconfig to the rules you're deleting now. Otherwise the autoformat will go haywire. :D |
Will do - can I do this in another PR? |
|
I've dumped the IDE settings to |
MrKrisKrisu
force-pushed
the
dev-ks/ide
branch
from
e21c13e to
afb5cb2
Compare
|
Announcement: #3079 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request removes IDE-specific configuration files (.idea, .vscode) from the repository to maintain a cleaner and more consistent codebase.
Changes:
🔥 Removed existing IDE configuration files from the repository.
🙈 Updated .gitignore to prevent committing IDE-specific files in the future.
Why:
IDE-specific files are personal to individual developers and should not be included in the shared repository. This ensures a more universal setup across different development environments and avoids unnecessary conflicts or clutter.
Discussion:
For cross-project settings, it's better to rely on standard tools like .editorconfig to define consistent coding styles and configurations. This approach ensures all contributors can follow the same standards, regardless of their development environment.
Important
Before pulling the changes here, make sure to back up your local IDE settings if needed. The removal of these files from the repository means they will no longer be available, and you might lose custom configurations that are important for your workflow. Save them locally to avoid any disruptions!