graphql-engine
hasura/graphql-engine/AGENTS.md
When creating pull requests, always read .github/PULLREQUESTTEMPLATE.md first and use it as the basis for the PR body. Make sure to fill in the correct checkboxes and put your changelog entry in the appropriate spot. This is used for release automation so the structure needs to stay intact. For any haskell code changes use cabal build all --enable-tests --enable-benchmarks to check your work and iterate until it builds cleanly. Make sure to always do a final pass with the above…
What's in it
- AGENTS.md
- Pull Requests
- Building and typechecking
- Third-party dependency docs
# AGENTS.md ## Pull Requests When creating pull requests, always read `.github/PULL_REQUEST_TEMPLATE.md` first and use it as the basis for the PR body. Make sure to fill in the correct checkboxes and put your changelog entry in the appropriate spot. This is used for release automation so the structure needs to stay intact. ## Building and typechecking For any haskell code changes use `cabal build all --enable-tests --enable-benchmarks` to check your work and iterate until it builds cleanly. Make sure to always do a final pass with the above before concluding your work! ## Third-party dependency docs `docs/docs/enterprise/dependencies.mdx` publishes a single table of the third-party dependencies (name, version, license) shipped by the Haskell server, the Go CLI and the frontend console. Whenever you add, remove or upgrade a dependency in any of these, update the matching rows in that table in the same change: - **Haskell server** — direct dependencies of `server/graphql-engine.cabal`, with the resolved version from `cabal.project.freeze`. - **Go CLI** — modules from `cli/go.mod`, in the `go-licenses report` format (license URL pinned to the module version). - **Frontend console** — the `dependencies` (not `devDependencies`) of `frontend/package.json`, with the version actually resolved in `frontend/yarn.lock` (not the `^`/`~` range) and the `license` field from the installed package. Keep each section's existing ordering, preserve the file's LF line endings, and format with `docs/.prettierrc.json`.
More agent context in hasura/graphql-engine
2 other files this repository gives its agents.
AGENTS.md
CLAUDE.md
Discussion
Evidence it works
Elsewhere, people who say they tested it. Read them for what they measured.
- Jun 21, 2020 · Stack Overflow · Why do subscriptions load the processor 100%
Talked about elsewhere, linking to hasura/graphql-engine
- Show HN: Hasura – Fast, instant GraphQL APIs on Postgres
Hacker News · 382 points · 103 comments · Jul 16, 2018
- Run Hasura without Docker
Stack Overflow · 8 votes · May 7, 2020
- github.com/hasura/graph...
Bluesky · @osrepos.bsky.social · 1 likes and reposts · Dec 15, 2024
- sql: add support for Hasura
GitHub · cockroachdb/cockroach · 12 reactions · 15 comments · Nov 3, 2021
- Scaling to 1M active GraphQL subscriptions on Postgres
Hacker News · 353 points · 80 comments · May 31, 2019
- how to make a case-insensitive graphql query?
Stack Overflow · 6 votes · Aug 25, 2020
- Hasura support or compatibility
GitHub · questdb/questdb · 7 reactions · Jun 1, 2021
- Streaming data in Postgres to 1M clients with GraphQL
Hacker News · 192 points · 73 comments · Oct 16, 2022
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
No reports yet. Be the first to say whether it worked.
Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.

