Andres G. Aragoneses

Update docs to not use resolutionPath?

2

**Describe the bug** Now that specific nuget packages exist for each DB type, shouldn't the docs be updated to not use resolutionPath in the samples? Of course another specific chapter...

When using FSharpLint it's usual to refer to the reports that the rules generate as "errors" or "warnings" or "suggestions", and the first two are easily confused with compiler errors/warnings...

In FSharpLint code itself: TrailingNewLineInFile.fs L14, ...

We use the `git describe` command to prevent release-notes commits to create nuget prereleases for commits that have already been tagged as a "non-pre" release; see: fa788dbdeddb2984503a24565547f72d93ef4311 However, this stopped...

Reason is we found a breaking change in .NET8, so we have decided to maintain .NET6 in the stable branch, and only have a .NET6->.NET8 migration path in the master...

Seq extensions: add trySkip

6

This way it is an alternative to Seq.skip: same but non-partial function (that doesn't throw exceptions), following same approach as tryHeadTail[1]. [1] https://github.com/fsprojects/FSharpx.Collections/commit/fdbeaf21db4bfc0f446abbbf8b70d2bb60e5e65d