Arnaud
43088759cf
Two related bugs in the Gitea issue body: 1. Attachments were always plain bullet links (`- url`), even for images — so they never rendered as a preview in the Gitea issue, just a clickable URL. Image content-types now use markdown image embed (``). 2. The admin "Create Gitea issue" retry action built its own body from scratch (`ticket.description` only) and never queried attachments at all — a retry always lost them, regardless of point 1's fix. Extracted buildGiteaIssueBody() to lib/gitea.ts so both the initial ticket-creation path and the retry path share one body-building implementation instead of two independent (and inevitably diverging) ones. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.