Attachments
Every request form takes files: a customer drops them on the form or chooses them with Add attachment, before they submit. There is no File field type — attachments belong to the request, not to one question on it.
Where files are stored
Section titled “Where files are stored”Pealboard stores them, not GitHub. GitHub’s own issue-attachment path is not available to a GitHub App: there is no documented API for it, so no application can use it.
Files are stored in Cloudflare R2 under the workspace and portal, and linked from the issue body as a signed URL. The signature lasts 30 days and Pealboard re-signs the link every time the issue is rendered, so the link in the body keeps working for as long as the request exists and a copied link stops working after 30 days.
Limits
Section titled “Limits”| Maximum size per file | 10 MB |
| Files per request | 10 |
| Accepted types | png, jpg, jpeg, gif, webp, svg, mp4, mov, webm, pdf, txt, log, zip |
A file that is too large or of a type that is not accepted is refused at the point of upload, with the reason stated. Nothing partial is created. The type is read from the file’s own bytes, never from its name, so renaming one changes nothing.
What an engineer sees
Section titled “What an engineer sees”A line in the issue body listing the file name, its size and its type, each linked. Following the link downloads the file; the engineer does not need a Pealboard account.
Deleting an attachment
Section titled “Deleting an attachment”Deleting a customer’s account deletes every file they uploaded, and rewrites the links in the bodies Pealboard authored to say the attachment was removed. Deleting one file on its own is not available yet.