Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.  This is especially recommended for binary packages to ensure reproducibility, and is more commonly ignored for libraries.

This is taken from https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control

with "main".

Merge main branch into master branch

Create Syncthing.gitignore

doc(readme): master branch is now main

[Node] Use real conventions

Added LensStudio.gitignore (Ted Brown)

Remove nuget.config from VisualStudio.gitignore

feat(node): added `.stylelintcache` for stylelint

Add vuepress v2.x temp and cache directory

Go: Ignore Go workspace file go.work

Ignore default Recordings folder created by Unity Recorder package

Update and fix WordPress gitignore

Update VisualStudio.gitignore

Co-authored-by: Jaan Jahilo <jaanjahilo@outlook.com>

added file extensions when glossaries is loaded with "symbols" option

Remove .idea folder from VisualStudio

AL Language gitignore template

Add `.RDataTmp` to R.gitignore

Update .gitignore for Idris 2

Update Unity.gitignore

Adds a relationship question

[Android] Cleanup and remove legacy stuff

Feel free to open a new PR for discussion on this.

When saving `.RData`, all data is initially saved in `.RDataTmp` which
is then renamed to `.RData`.

`.RDataTmp` should be added to `.gitignore` since it will only exist
while a save operation is in progress or something failed on save.

Relevant links:
- https://stackoverflow.com/questions/32098036/purpose-of-rdatatmp-temporary-file-r
- https://github.com/wch/r-source/blob/trunk/src/library/base/R/load.R#L145-L154

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

https://www.kicad.org/blog/2021/10/Avoid-links-to-former-kicad-domain/

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."

Version 0.89.0 of Hugo creates a new `.hugo_build.lock` lock file
when building the site.

The release notes suggest adding this to the `.gitignore`:
https://github.com/gohugoio/hugo/releases/tag/v0.89.0