A GitHub issue for every submission
A public bug form, a beta feedback form or a request form for your open-source project can file its own issues. Each submission opens one in the repository you pick, with the title and body you wrote and the answers in GitHub-flavored Markdown.
Updated
How it works
- Open the form’s Integrations, pick GitHub Issues, and connect a GitHub account or pick one already connected. Pick the repository, and a milestone if every issue belongs to one.
- Write the title and the body. Type @ to insert an answer or the PDF link. The title is plain text up to 256 characters; the body is GitHub-flavored Markdown.
- Click Turn on GitHub Issues, then Send test to create a real issue with a
[Test]prefix, which you close afterwards.
What the issue carries
A file upload shows its name and a download link. An empty title falls back to “New submission to” followed by the form’s name. Formstep creates one new issue per submission and never comments on an existing one; if you triage by label, add it with your own GitHub automation.
When someone does not finish
On Pro and Business, a public-link response left unfinished for 12 hours, a day, three days or a week can open an issue of its own, with the partial-submission label Formstep creates the first time, and a title and body written for that case.
When delivery fails
GitHub tokens do not expire. If you revoke the grant, the next delivery fails, the connection expires, and the person who set it up gets an email; Reconnect restores it. An archived or deleted repository fails with not found until you pick another. Deliveries are tried up to five times, and after five failures in a row the integration pauses until you fix the cause and click Resume.
The same form can post to Discord or Slack at the same time, and a team on Linear has the same integration there.
