Contributing to pg_ducklake

August 4, 2026 ยท View on GitHub

Thanks for your interest in pg_ducklake! All types of contributions are welcome.

You don't have to write code to help

We develop in a vibe coding style -- AI coding assistants help us ship code fast. What we can't generate is your perspective as a user. The contributions that help us most are often:

  • Bug reports -- a short description with steps to reproduce is perfect.
  • Feature requests -- tell us what you wish pg_ducklake could do.
  • Questions and discussions -- confused by something? Others probably are too.
  • Docs and examples -- spotted something unclear? A small fix can save the next person a lot of time.

Don't underestimate these -- a good bug report or feature idea can shape the project more than a pull request.

Code contributions are welcome too

Bug fixes, new features, tests -- we're happy to review them. For anything non-trivial, please open an issue first so we can discuss the approach.

Pull requests

Keep the pull request description brief and written for human reviewers. Focus on why the change is needed and any context, tradeoffs, or decisions that are not obvious from the diff. Do not summarize the code. Omit routine testing sections when CI already provides the relevant result; mention testing only when manual or non-CI validation adds useful review context.

If your PR description is AI generated, end the description with this unchecked review checklist:

- [ ] This PR has been reviewed by human.
- [ ] This PR description has been reviewed by human.

Only a human reviewer should check these items.

Reporting a bug

Open an issue with:

  1. What you did (SQL statements, configuration, environment)
  2. What you expected
  3. What actually happened (error messages, logs)

Suggesting a feature

Open an issue describing:

  1. The problem you're trying to solve
  2. How you'd like it to work

A few sentences is plenty. We'll figure out the details together.