About the GitShowcase Forum for developers
The GitShowcase Forum is a question and answer space for developers, served at gitshowcase.com/forum/ as a section of GitShowcase. It exists for two things. The first is practical questions about shipping real projects: the CI job that fails only on main, the Postgres pool that runs dry on a serverless deploy, the webhook that fires twice. The second is feedback on work you have already built, such as a GitHub repo, a side project, a profile README or a portfolio.
Reading needs no account. You can browse sections, open threads and search without signing in. To ask or reply you sign in with an email address, as the privacy page explains.
The 12 sections
Each section has its own page under /section/. Two are open discussions and ten are question and answer.
- Show Your Project for Feedback: share a repo, side project or demo and get specific notes on the code, docs and stack. This is the only place for promoting your own work.
- Portfolios, READMEs and Profiles: what reviewers read, what to cut and how to show real work.
- AI APIs and LLM Integration: rate limits, streaming, tool calls, structured output and cost control.
- MCP Servers and Agent Tooling: transports, auth, permissions and debugging tool calls.
- Databases and Vector Stores: Postgres hosting, pooling, migrations and vector search.
- Hosting, Edge and Deploys: Workers, Vercel, Netlify, Fly and containers, plus caching and limits.
- Auth, Backends and BaaS: sessions, OAuth, passkeys and row level security.
- CI/CD and GitHub Actions: workflow syntax, caching, secrets, OIDC deploys and flaky tests.
- Observability and Debugging in Production: logs, traces, metrics and alert noise.
- Payment, Email and SMS APIs: webhooks, idempotency, deliverability and sender registration.
- Open Source Maintainers: licenses, triage, releases and security reports.
- Editors and AI Code Assistants: setup, rules files, review habits and privacy settings.
Who answers
Two staff moderators answer and keep the sections in order. Their answers carry a staff label.
Maren Castillo is the forum lead for databases, hosting, CI and production. She asks for versions, config and the exact error before answering, links the vendor docs and changelogs she checked, and says when a limit or price model changed recently.
Nils Haugen is the APIs and tooling editor, covering LLM, MCP, payments and portfolios. He answers from provider docs and specs, shows the request or config that works, and gives project and README feedback specific enough to act on.
Members answer too, and member answers are personal experience that staff do not check before they appear. A staff label tells you which is which.
How answers use sources
Developer advice goes stale quickly. A rate limit, a free tier or a default setting can change between releases. So staff answers lean on primary sources: vendor documentation, changelogs, release notes and the specifications themselves. When an answer states a limit, a version or a behavior, it says where that came from and what date the claim was checked against. If you are on a different version, the answer should tell you what to compare.
When a source changes, we add a visible note to the thread rather than rewriting it quietly. If you spot an answer that is out of date, tell us through the contact page and include the link to the page that shows the current behavior.
A few threads to start with
Early staff answers include:
- Why is my GitHub Actions cache never restoring between runs?
- How should I write a README so people actually try my project?
- How do I stop hitting 429 rate limits when calling an LLM API in production?
- Serverless Postgres keeps running out of connections. What should I pool with?
- What is an MCP server, and when is it worth building one instead of a plain API?
Before you post
Read the guidelines and the terms. The short version: name your stack and versions, quote the exact error, put code in fenced blocks and never paste a key, token or connection string.
Who answers here
Maren Castillo
Forum lead: databases, hosting, CI and production
Maren moderates the infrastructure sections. She asks for versions, config and the exact error before answering, links the vendor docs and changelogs she checked, and says when a limit or price model changed recently.
Nils Haugen
APIs and tooling editor: LLM, MCP, payments and portfolios
Nils moderates the API, agent tooling and portfolio sections. He answers from the provider docs and specs, shows the request or config that works, and gives project and README feedback that is specific enough to act on.