Conflicts with JetBrains.gitignore. Some files in this directory should be checked in.
Not sure about *.sln.iml, so I'm leaving that. The JetBrains.gitignore file contains commented-out IML stuff with instructions on when to uncomment.
With Go 1.18, support for Go workspaces will land.
Go workspaces are configured in `go.work`, which
contains paths to local development versions of
modules and therefore is not expected to be
commited.
See:
* https://github.com/golang/go/issues/45713
Three new files to ignore for GoHugo repositories:
- `/assets/jsconfig.json` - Quote from [JavaScript Building](https://gohugo.io/hugo-pipes/js/): "Hugo will, by default, generate a assets/jsconfig.json file that maps the imports. This is useful for navigation/intellisense help inside code editors, but if you don’t need/want it, you can turn it off."
- `hugo_stats.json` - Quote from [Post Build Resource Transformations ](https://gohugo.io/news/0.69.0-relnotes/): "The prime current use case for the above is CSS pruning in PostCSS. In simple cases you can use the templates as a base for the content filters, but that has its limitations and can be very hard to setup, especially in themed configurations. So we have added a new writeStats configuration that, when enabled, will write a file named hugo_stats.json to your project root with some aggregated data about the build, e.g. list of HTML entities published, to be used to do CSS pruning."
- `.hugo_build.lock` - Quote from [Fine Grained File Filters ](https://gohugo.io/news/0.89.0-relnotes/): "Hugo now writes an empty file named .hugo_build.lock to the root of the project when building (also when doing hugo new mypost.md and other commands that requires a build). We recommend you just leave this file alone. Put it in .gitignore or similar if you don’t want the file in your source repository."
If a user has ignored an asset (no matter how dubious that decision may be), they also want to ignore the .meta file. Instead of bringing back .metas that have been ignored, this template should trust that a user has ignored the files they want to ignore.
You'd encounter this issue if you had added an ignore for an asset and its meta above this Unity template, or if another template ignored an asset and meta.
In general excludes may be dangerous in these templates, as they can have unintended consequences on other templates.
