Ignoring the .idea and .vscode folders makes working with the Koha repo using IntelliJ IDEA or VS Code easier. Patch incoming.
Created attachment 169991 [details] [review] Ignore .idea and .vscode
Rudolf, I believe this is ready for others to look at? If so, you should update its status to "Needs Signoff" or else it won't show up in people's TODO lists.
Oh, I forgot that. Thanks
Created attachment 169999 [details] [review] Bug 37556: Add project folders of popular IDEs to .gitignore Ignoring the .idea and .vscode folders makes working with the Koha repo using IntelliJ IDEA or VS Code easier. To test: 1. Clone the Koha repo. 2. Open the repo folder in an IDE like IntelliJ IDEA or VS Code. 3. Observe that the IDE creates an .idea or .vscode folder but does not try to commit it. Sponsored-by: Reformational Study Centre <www.refstudycentre.com> Signed-off-by: Pedro Amorim <pedro.amorim@ptfs-europe.com>
Just in case you don't already know: you can ignore these files without touching .gitignore, either globally using $HOME/.config/git/ignore or locally using .../koha/.git/info/exclude I use that to ignore vim temporary files.
(In reply to Julian Maurice from comment #5) > Just in case you don't already know: you can ignore these files without > touching .gitignore, either globally using $HOME/.config/git/ignore or > locally using .../koha/.git/info/exclude > I use that to ignore vim temporary files. I can confirm that this works. I looked it up remembering Julian hat pointed it out a while ago. I was going to suggest adding a hint to the wiki, only to realize it's already there :) https://wiki.koha-community.org/wiki/Koha-testing-docker Maybe this would be better than adding IDE specific code to Koha codebase?
> Maybe this would be better than adding IDE specific code to Koha codebase? Sorry to nit-pick here, but it's IDE-specific config, not IDE-specific code (i.e., it has no effect on the end product, only on the developer experience). It's conceptually similar to something like `.editorconfig`. It's standard practice in many projects that I have seen to have IDE-specific stuff in `.gitignore`. The reason why I would not want to do this in my `.git` settings, it because I have other projects on my machine where `.idea` and/or `.vscode` should not be ignored.
> It's conceptually similar to something like `.editorconfig` Except .editorconfig is not specific to a single editor/IDE and *should* be committed to the repository. How are they similar in this context ? (In reply to Rudolf Byker from comment #7) > The reason why I would not want to do this in my `.git` > settings, it because I have other projects on my machine where `.idea` > and/or `.vscode` should not be ignored. You can still ignore it in the repository specific .git/info/exclude file, or ignore it globally and then de-ignore it in a project specific file. Honestly it's easier than asking every project you work on to add rules for your preferred tools. (Never had seen a .swp file even once since I learned that ;))