!RbXGJhHMsnQcNIDFWN:nixos.org

Haskell in Nixpkgs/NixOS

700 Members
For discussions and questions about Haskell with Nix, cabal2nix and haskellPackages in nixpkgs | Current Docs: https://nixos.org/manual/nixpkgs/unstable/#haskell | Current PR: https://github.com/nixos/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Ahaskell-updates | Maintainer Docs: https://github.com/NixOS/nixpkgs/blob/haskell-updates/pkgs/development/haskell-modules/HACKING.md | More Nix: #community:nixos.org | More Haskell: #haskell-space:matrix.org | Merger Schedule: https://cloud.maralorn.de/apps/calendar/p/H6migHmKX7xHoTFa/dayGridMonth/now | Join #haskell.nix:libera.chat for question about the alternative haskell.nix infrastructure137 Servers

Load older messages


SenderMessageTime
22 Feb 2026
@maralorn:maralorn.demaralorn aiya: I am not aware of any rule. At least when you are opening the PR from your fork. 22:50:49
23 Feb 2026
@acidbong:envs.netAcid Bong
In reply to @aiya:catgirl.cloud

i understand that PR titles are for the affected titles but my question is for conventions on branch names: if i want to merge a PR into haskell-updates, what should my branch name be? must it start with haskell-updates? (i.e. haskell-updates-fix-pkg versus fix-pkg

I believe head:haskell-updates filters for all PRs targeting the haskell-updates branch

i believe that would be base:haskell-updates, head filters on your branch name

your branch name doesn't matter at all, only commit and PR description and contents
20:12:06
@acidbong:envs.netAcid Bong* your branch name doesn't matter at all, only commit and PR description and contents, and the branch you're targeting20:13:29
@magpi:matrix.orgLuke changed their display name from magpi to Luke Worth.21:17:08
@magpi:matrix.orgLuke changed their display name from Luke Worth to Luke.21:17:40

There are no newer messages yet.


Back to Room ListRoom Version: 6