Please update your Pull Request title to mention that it's affecting Unity: it's hard enough to browse through more than a hundred pending pull requests. Thank you.

@Coeur Done. Sorry for the inconvenience!

@jdpoenisch thanks for the contribution!

There isn't really one, this is just my experience.

Does anyone else agree or disagree with this change?

cc @Flate @shana @johnsoncodehk @FutureClemens @ksmit799 @LucasSteer @matzar @cscharfen

The library folder is a cache folder, and as such would only serve to clutter commits. Rather then relying on cached configuration options, I would recommend setting up your own build scripts to simplify the building process across devices (see here).

The library folder is a cache folder, and as such would only serve to clutter commits. Rather then relying on cached configuration options, I would recommend setting up your own build scripts to simplify the building process across devices (see here).

That's true in general for the Library folder .. that's why it is ecluded by the gitignore already.

Just as said for me it made sense to keep at least some of the *.asset files and rather to implement additional methods for something that actually already exists in the UnityEditor I decided to simply keep them and never had to worry about switching the platform or adding all scenes again to the build settings when cloning to a new device.

I noted there are some that really make no sense to keep as they change every time like e.g.
Library\InspectorExpandedItems.asset

but I definitely want to keep e.g.
Library\BuildSettings.asset
Library\EditorUserBuildSettings.asset
Library\EditorUserSettings.asset
Library\ProjectSettings.asset

You're free to make your own local changes, however in general I think many developers would not want their build configurations being tracked by git. This is especially true when working on multi-team projects, as there will often be several different developers building with different configurations simultaneously.

In a simple case, osx and windows build settings are not common, like ios build only exists in osx and not in windows.

You're free to make your own local changes, however in general I think many developers would not want their build configurations being tracked by git. This is especially true when working on multi-team projects, as there will often be several different developers building with different configurations simultaneously.

Absolutely true!
Plus: Generated files shall not be submitted to the git repo. Use shared Cache Servers to share cached & generated files, but not git.

The library folder is a cache folder, and as such would only serve to clutter commits. Rather then relying on cached configuration options, I would recommend setting up your own build scripts to simplify the building process across devices (see here).

You're free to make your own local changes, however in general I think many developers would not want their build configurations being tracked by git. This is especially true when working on multi-team projects, as there will often be several different developers building with different configurations simultaneously.

Absolutely true!
Plus: Generated files shall not be submitted to the git repo. Use shared Cache Servers to share cached & generated files, but not git.

It seems like it would require some extra set-up for .gitignore to work properly, so I wouldn't add it to the official one which should work out-of-the-box, without any extra set-up.

Mark, I've put Library/*.asset into my .gitignore in the past; used that .gitignore from the first commit onward; did not store Library/*.asset anywhere else; lost all my local copies and effectively lost all of my Library/*.asset files.

Regardless, I'd say there might be an argument against putting this one into the official .gitignore.

cc: @shiftkey @ksmit799

@der-hugo It is probably to late to tell you now or you already figured it out yourself, but in case not or someone else comes across this, you might be interested in Unity Cache Server / Unity Accelerator depending on your Asset Import Pipeline.