On 13 Nov 2026, at 11:59, Andreas Klebinger via ghc-devs <ghc-devs@haskell.org> wrote:_______________________________________________Hello devs,
I've been using a local sqlite3 cache of all ghc tickets/mrs and some more on top for a while now with agents as interface to the data.
While it's a shame that this works so much better than gitlabs search it is what it is. So I want to share what I've been using to get
a better answer faster for questions like:
* Is there already a ticket about <thing> already.
* I remember <person> wrote a comment about <thing>, what MR/ticket was this on.
* What ghc versions have the fix to <ticket> already.
I use a small haskell tool + skill file to create/update the data which can be found here: https://github.com/AndreasPK/fetch-gitlab
and I want to encourage people to try it. And if they find it worse than what they use today complain to me so I can make it better.I don't think my version of this is particularly perfect (It's a lot of generated and only lightly reviewed code) . But I hope to avoid everyone vibing their own version and instead sharing one
implementation and improving that one together.If you want to try it clone: https://github.com/AndreasPK/fetch-gitlab.git
Install via cabal install, ideally also install thesqlite3binarySemi-Optional: Download a snapshot of gitlab.db from https://drive.google.com/file/d/1zJG6LonseOmarMhE2OZbV6Yr7iaOzN8D/view?usp=drive_link
Place it under ~/.fetch-gitlab/gitlab.db
This can be skipped but then the initial sync will take hours.Create a read-only api_read token under ~/.fetch-gitlab/gitlab-tokenOptional: Run fetch-gitlabto fetch the latest MRs/Ticketscp skills/fetch-gitlab/ ~/.claude/skills/to install the claude skill (adjust if you use a different setup)The skill triggers on things like "ghc gitlab" "ghc ticket(s)" and "ghc mr". Personally I found this much faster than trawling through gitlab by hand.
It's not magic, and all the usual disclaimers about AI apply. (E.g. it can miss tickets and what not). But it turns out an agent grepping through
all tickets at once easily beats gitlabs search somehow. So I have been pretty happy with it.
Here are two examples to give people an idea.
<vZO66K0Ae1KTxsTZ.png><Jnu0EmCdxOnmsZM0.png>
ghc-devs mailing list -- ghc-devs@haskell.org
To unsubscribe send an email to ghc-devs-leave@haskell.org