展示HN：GitForms – 使用GitHub Issues作为数据库的零成本联系表单

展示HN：GitForms – 使用GitHub Issues作为数据库的零成本联系表单
Show HN: GitForms – Zero-cost contact forms using GitHub Issues as database

原始链接: https://gitforms-landing.vercel.app/

## GitForms：将 GitHub Issues 用作表单后端 - 摘要 GitForms 利用 GitHub Issues 作为免费且出人意料地强大的表单后端。GitHub 的 API 提供慷慨的限制 – **每小时 5,000 次请求**（轻松处理每月数万次提交）和 **无限存储**。电子邮件通知会自动启用且可自定义。该系统符合 **GDPR 规定**，因为您控制着 GitHub 仓库中的数据，并提供删除和隐私策略选项。它拥有 **99.9% 的正常运行时间**，并允许以各种格式轻松**导出**数据，避免供应商锁定。虽然设置简单（需要基本的 Vercel/GitHub token 知识），但需要注意的是，这是一种 GitHub Issues 的*创造性*用法。它非常适合 **个人项目和原型**（每月 10-100 次提交）。对于 **高流量商业网站**，建议使用传统的数据库解决方案，如 Supabase 或 Airtable。

## GitForms：使用 GitHub Issues 的零成本联系表单开发者 lgreco 创建了 **GitForms**，一个开源的联系表单解决方案，旨在避免像 Typeform 这样的服务的月费。它利用 GitHub Issues 作为数据库：表单提交会在 GitHub 仓库中创建新的 issue，从而触发免费的邮件通知。该项目使用 Next.js 14、Tailwind 和 TypeScript 构建，设计用于易于部署在 Vercel/Netlify 上，并通过 JSON 进行配置。该项目引发了争论，主要围绕名称（“GitForms”）违反 Git 的商标政策。人们也对依赖 GitHub 的服务表示担忧，考虑到他们最近的价格变化以及该项目的长期可行性。一些评论员指出了类似的项目，如 Utterances，并强调了创建此类解决方案的简易性，质疑其作为一项业务的潜力。尽管存在对登录页面声明准确性的批评（许可、GDPR 合规性、正常运行时间），许多人认为这个概念是一个巧妙的技巧，并且非常适合 MVP 和低流量的使用场景。

原文

What are GitHub's limits?

GitHub has generous limits for Issues API. Free accounts get 5,000 requests per hour and unlimited Issues creation. For most websites, this means thousands of form submissions per month at no cost. Storage is unlimited - your contact data lives in Issues forever.

Will I hit the rate limit?

Unlikely. 5,000 requests/hour means you can handle ~120,000 submissions per day. For context, most landing pages get 10-100 submissions per month. Even viral campaigns stay well within limits.

How do email notifications work?

GitHub automatically emails you when a new Issue is created. No configuration needed. You can customize notification settings in your GitHub account - choose instant emails, daily digests, or disable them.

Is this GDPR compliant?

Yes. You control the data since it's stored in your own GitHub repository. Add a privacy policy explaining where contact data is stored. You can delete Issues anytime, and users can request deletion under GDPR.

Can I use this for production sites?

Absolutely. GitForms uses GitHub's stable API with 99.9% uptime. Thousands of sites use GitHub Issues for production workflows. It's more reliable than many paid form services.

What if GitHub changes their API?

GitHub maintains backward compatibility and announces changes months in advance. Since you own the code, you can adapt quickly. The Issues API has been stable for over 10 years.

Can I export my data?

Yes, anytime. Use GitHub's API to export all Issues as JSON, CSV, or any format. You can also migrate to a different system - no vendor lock-in.

Do I need technical knowledge?

Basic knowledge helps but isn't required. If you can deploy to Vercel and create a GitHub token, you can use GitForms. Setup takes 5 minutes with our step-by-step guide.

Is this the intended use of GitHub Issues?

Honestly, no. GitForms uses GitHub Issues creatively as storage. While technically compliant with API terms, it's best suited for personal projects and prototypes (10-100 submissions/month). For high-traffic commercial sites, consider traditional databases like Supabase or Airtable.