Is it a good idea to ignore the whole .<ij/as/cl>wb folder?

[ynty]

Both GitHub and gitignore.io has this content in their gitignore template for Bazel

# Directories for the Bazel IntelliJ plugin containing the generated
# IntelliJ project files and plugin configuration. Separate directories are
# for the IntelliJ, Android Studio and CLion versions of the plugin.
/.ijwb/
/.aswb/
/.clwb/

to ignore all files under .<ij/as/cl>wb.

But I found that now some file is under these folders:

• .bazelproject file (project view).
• .idea folder which contains all configs for JetBrains IDE, including something you might want to share with anyone who edit this repo with you, such as code style, copyright template, etc. If a project is imported to JetBrains IDE as a Bazel Project, the .idea folder will always generated under .<ij/as/cl>wb folder.

[odisseus]

It is common practice to ignore both .ijwb and .idea, and let the IDE generate these files upon project import.

If you want to pre-define project views, you may store them in a different directory (example). Upon project import, the user can choose one of those project view files (which will be imported into .ijwb/.bazelproject), or define his own project view from scratch.

If you have other reasons to store the .idea directory, you can define an exclusion in your gitignore file like this (explanation):

/.ijwb/*
!/.ijwb/.idea

[ynty]

If you have other reasons to store the .idea directory, you can define an exclusion in your gitignore file like this (explanation):

/.ijwb/*
!/.ijwb/.idea

I tried this but quickly found that when importing the project on a new computer, everything under .<ij/as/cl>wb will be overwritten and re-generated by the Bazel plugin, so does the .<ij/as/cl>wb/.idea folder, ALL files in this directory(.<ij/as/cl>wb/.idea) cannot be retained (including scopes and copyright statements settings).