Daniel Esik

Maintaining naming consistency is crucial within a single abstraction, though it's not _that_ big of a deal, since we don't have a universally agreed-upon language. Regarding the `Foldable` + `MonadThrow`...

> valid None and invalid "more-than-one" values... What stops us from having `ensureEmpty` and/or `ensureSoleOrEmpty`? `sole` is unambiguous here, meaning 'being single'.

> Shouldn't ensureSole (ie unique in doobie) just return an A? Use case is we expect exactly one item, or else its error. I was suggesting adding `ensureSole` directly to...

FWIW, to get the site updated, we need to merge this into `main`

Thanks for opening this. > I have created a self-contained reproducer in this gist, against both 0.23.x and 1.0.0 IIUC, your example can be ported into a unit test where...

Currently, CI is failing with ``` [error] /home/runner/work/http4s/http4s/server/shared/src/main/scala/org/http4s/server/middleware/BracketRequestResponse.scala:241:14: Variable releaseWarning undefined in comment for method bracketRequestResponseAppR in object BracketRequestResponse [error] * @note $releaseWarning ``` Which is [a known regression](https://github.com/scala/bug/issues/13129) in...

Oh okay, CE 3.6.x is still on SN 0.4.

Ouch, CI is red.

Hmm, I don't think it's _valid_ to compare the normalization of `java.net.URI` with that of `org.http4s.Uri.Path`. Technically, they're distinct entities with different scopes. But anyway, I also don't think that...

I was just thinking again about adding a dedicated SBT setting for the fork condition. Maybe introducing `githubWorkflowForkCondition` with a default value of `github.event.repository.fork == false` isn't such a bad...