3 Commits

Include renames

Author	SHA1	Message	Date
jochen	ac90b35b49	guard.ts: cover every branch for a rule Go's regexp reads otherwise, and hold both matchers to one table (issue 539) ... Review 30 found guard.ts missing branches the forge protects: Go reads \d, \w, \pL, a class opening with ] or ^, and [[:digit:]] otherwise than JavaScript. A rule using any of them now covers every branch, so the guard refuses more than the forge, never less. test/rule-cases.json holds the forge's answers, read by the Go and TypeScript tests alike.	2026-10-12 12:51:22 +02:00
jochen	f2d765320a	gitea forge bundle: name the parent the forge used, match protection rules as the forge does, bound a commit's size and a search's time (issue 539) ... The forge's contents and diffpatch endpoints take a branch, never a commit to build on, so the parent is read from the commit the forge made, and a branch that moved under the commit is said. Blobs are read at the commit read first, not at the branch name. Protection rules match as Gitea 1.27 matches them ([...], {a,b}, escapes, a plain name in any case), in the Go bundle and in guard.ts alike. One commit carries at most 4 MiB per file or patch and 16 MiB together; code search stops at its deadline and says so. The HTTP client the two Go bundles copied is one package, internal/forgehttp.	2026-10-12 12:51:22 +02:00
jochen	9eb2ea8d69	gitea: let an agent put a commit on a branch of its own, and read history, compares, reviews, directories and code (issue 375) ... An agent could not get a finished change onto the forge without someone pushing by hand, so the branch / pull request / approval rule could not be followed. A Go bundle serves gitea_commit, held to gitea_api's rule (never the default branch, never a protected one), and the summarised reads agents otherwise made through gitea_api as raw JSON.	2026-10-12 12:06:23 +02:00