Merge master into haskell-updates

# postgresql: move packages.nix to ext/default.nix

719034f6f6749d624faa28dff259309fc0e3e730

# php ecosystem: reformat with nixfmt-rfc-style

75ae7621330ff8db944ce4dff4374e182d5d151f

c759efa5e7f825913f9a69ef20f025f50f56dc4d

# pkgs/os-specific/bsd: Reformat with nixfmt-rfc-style 2024-03-01

3fe3b055adfc020e6a923c466b6bcd978a13069a

/pkgs/applications/networking/cluster/terraform-providers @zowoq

# Forgejo

nixos/modules/services/misc/forgejo.nix      @bendlas @emilylange

pkgs/applications/version-management/forgejo @bendlas @emilylange

nixos/modules/services/misc/forgejo.nix @adamcstephens @bendlas @emilylange

pkgs/by-name/fo/forgejo/package.nix     @adamcstephens @bendlas @emilylange

# Dotnet

/pkgs/build-support/dotnet                  @IvarWithoutBones

    # While `edited` is also triggered when the PR title/body is changed,

    # this PR action is fairly quick, and PR's don't get edited that often,

    # so it shouldn't be a problem

    # There is a feature request for adding a `base_changed` event:

    # https://github.com/orgs/community/discussions/35058

    types: [opened, synchronize, reopened, edited]

permissions: {}

# Create a check-by-name concurrency group based on the pull request number. if

# an event triggers a run on the same PR while a previous run is still in

# progress, the previous run will be canceled and the new one will start.

concurrency:

  group: check-by-name-${{ github.event.pull_request.number }}

  cancel-in-progress: true

# We don't use a concurrency group here, because the action is triggered quite often (due to the PR edit

# trigger), and contributers would get notified on any canceled run.

# There is a feature request for supressing notifications on concurrency-canceled runs:

# https://github.com/orgs/community/discussions/13015

jobs:

  check:

## How to merge pull requests

[pr-merge]: #how-to-merge-pull-requests

The *Nixpkgs committers* are people who have been given

To streamline automated updates, leverage the nixpkgs-merge-bot by simply commenting `@NixOS/nixpkgs-merge-bot merge`. The bot will verify if the following conditions are met, refusing to merge otherwise:

- the commenter that issued the command should be among the package maintainers;

- the package should reside in `pkgs/by-name`.

Further, nixpkgs-merge-bot will ensure all ofBorg checks (except the Darwin-related ones) are successfully completed before merging the pull request. Should the checks still be underway, the bot patiently waits for ofBorg to finish before attempting the merge again.

For other pull requests, the *Nixpkgs committers* are people who have been given

permission to merge.

It is possible for community members that have enough knowledge and experience on a special topic to contribute by merging pull requests.

    ln -s ${optionsDoc.optionsJSON}/share/doc/nixos/options.json ./config-options.json

  '';

  buildPhase = ''

  buildPhase = let

    pythonInterpreterTable = pkgs.callPackage ./doc-support/python-interpreter-table.nix {};

    pythonSection = with lib.strings; replaceStrings

      [ "@python-interpreter-table@" ]

      [ pythonInterpreterTable ]

      (readFile ./languages-frameworks/python.section.md);

  in ''

    cp ${builtins.toFile "python.section.md" pythonSection} ./languages-frameworks/python.section.md

    cat \

      ./functions/library.md.in \

      ${lib-docs}/index.md \