From 18cb856e4975843e80403bb6b5f1b2142bf3c36c Mon Sep 17 00:00:00 2001 From: sirily Date: Tue, 10 Mar 2026 15:21:07 +0300 Subject: [PATCH] docs: document gitea issue workflow --- AGENTS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 6e5d43c..1fa5062 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -47,3 +47,10 @@ This repository is a TypeScript monorepo for `nproxy`, a crypto-subscription ima ## Workflow - At the end of each completed task, create a PR for the changes unless the user explicitly says not to. + +## Gitea Workflow +- Treat the remote Gitea repository as the source of truth for task tracking when the user refers to `issues`. +- Before starting implementation, open the relevant Gitea issue and read its full problem statement and acceptance criteria instead of guessing from local notes. +- If the user asks to "continue work" or pick the next task, inspect the open Gitea issues and choose the first one that is logically ready to implement. +- After finishing the task, push the branch and create a Gitea PR linked to the issue, usually with `Closes #` in the PR body. +- If Gitea access requires credentials or network escalation, use the configured repository environment and approved escalation flow instead of skipping the issue lookup.