8 Commits

Author	SHA1	Message	Date
will.anderson	3a04b04f64	fix(ci): use semver-compatible version string for Gitea image ... Change GITEA_VERSION from 'neuron-<sha>' to '1.26.1-neuron.<sha>' so tea and other clients that parse the version can correctly identify it as 1.26.1-compatible and enable the full API surface.	2026-05-08 08:04:26 -05:00
will.anderson	83223bb939	ci: install docker buildx plugin; switch to buildx build --load ... DOCKER_BUILDKIT=1 requires the buildx plugin which isn't installed on the runner. Install it explicitly then use docker buildx build --load (outputs to local daemon so the push step can tag+push normally). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-07 19:01:46 -05:00
will.anderson	5393a85b04	ci: enable DOCKER_BUILDKIT for BuildKit FROM --platform support ... The Gitea Dockerfile uses FROM --platform=$BUILDPLATFORM which requires BuildKit. The GCE runner defaults to the legacy builder — set DOCKER_BUILDKIT=1 to enable it. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-07 18:57:30 -05:00
will.anderson	4e929ad814	ci: dev/stage/main branch build pipeline for custom Gitea image ... Build and push to Artifact Registry on merge to dev/stage/main: dev → gitea:dev stage → gitea:stage main → gitea:latest + gitea:<sha> Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-07 18:47:04 -05:00
will.anderson	3d9a09496d	fix(actions): use per-step status in workflow job API response; add build workflow ... ToActionWorkflowJob was calling ToActionsStatus(job.Status) for every step, making each step reflect the whole job conclusion instead of its own state. Replace the inline loop with the existing ToActionWorkflowStep helper which correctly uses step.Status. Add .gitea/workflows/build-push.yaml to build and push a Docker image to Artifact Registry on push to this branch, enabling deployment to GKE. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-07 18:46:18 -05:00
Lunny Xiao	1ed8e6aa5f	Update demo site location from try.gitea.io -> demo.gitea.com (#31054)	2024-05-27 15:05:12 +00:00
Lunny Xiao	476b9d1589	Use docs.gitea.com instead of docs.gitea.io (#26739)	2023-08-27 11:59:12 +00:00
Gabriel	a959ed99c2	Issue template form (#16349) ... * Create issue template using new format This issue template has been based off of the current issue creation workflow defined in the ISSUE_TEMPLATE.md file This commit allows for that issue template (which is a legacy method of creating an issue) to be deleted * Delete old issue template file This commit deletes the old issue template file, as it is both legacy and replaced by ISSUE_TEMPLATE/issue.yaml * Adjust file upload and remove code of conduct checkbox * Block blank issue creation * Update feedback Removed most requirements Updated prompt to include instruction to state whether using try.gitea.io Added default value to Gitea version * Create Feature Request issue form * Update and rename issue.yaml to bug-report.yaml * Enable blank issue creation Co-authored-by: a1012112796 <1012112796@qq.com> * Update config.yaml * Remove default & placeholder from Gitea version * Create issue template in .gitea directory * Add relevant bug report message to feature request * Adjust name to remove banner There is a banner that tells you to create a config.yml when you already have a config.yaml Renaming the file stops this from occurring. * Add UI bug report form * Remove unnecessary question Co-authored-by: a1012112796 <1012112796@qq.com> Co-authored-by: techknowlogick <techknowlogick@gitea.io> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lauris BH <lauris@nix.lv>	2021-09-15 20:33:13 +03:00