summaryrefslogtreecommitdiff
path: root/HACKING.md
diff options
context:
space:
mode:
authorChris Martin <ch.martin@gmail.com>2022-04-26 13:46:36 -0600
committerMarge Bot <ben+marge-bot@smart-cactus.org>2022-04-30 16:54:57 -0400
commitd0f14fadd41f7bf032c48c3eceeaff3a85318426 (patch)
tree29fc453cb89c1fc2fe2dc04266716b63b7b66a04 /HACKING.md
parentd8cbc77e755f418ec40f15c7785c16e7a0309722 (diff)
downloadhaskell-d0f14fadd41f7bf032c48c3eceeaff3a85318426.tar.gz
hacking guide: mention the core libraries committee
Diffstat (limited to 'HACKING.md')
-rw-r--r--HACKING.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/HACKING.md b/HACKING.md
index 8ae11bb94c..dbaeefc25b 100644
--- a/HACKING.md
+++ b/HACKING.md
@@ -64,6 +64,7 @@ Now, hack on your copy and rebuild (with `make`) as necessary.
Then start by making your commits however you want. When you're done, you can submit
a pull request on Github for small changes. For larger changes the patch needs to be
submitted to [GitLab](https://gitlab.haskell.org/ghc/ghc/merge_requests) for code review.
+Changes to the `base` library require a proposal to the [core libraries committee](https://github.com/haskell/core-libraries-committee/issues).
The GHC Wiki has a good summary for the [overall process](https://gitlab.haskell.org/ghc/ghc/wikis/working-conventions/fixing-bugs). One or several reviewers will review your PR, and when they are ok with your changes, they will assign the PR to [Marge Bot](https://gitlab.haskell.org/marge-bot) which will automatically rebase, batch and then merge your PR (assuming the build passes).