3 Commits

Include renames

Author	SHA1	Message	Date
mesh-toolsandClaude	d4b8b24701	Let gitea_commit take a large patch from a hash-checked spool file (issue 852) ... A feature's diff is megabytes, too large to type into a call. gitea_commit now also takes patch_file, the random hex name of a file in the module's spool directory /var/lib/mesh/forge-patches (mode 0733, owned by the machine's account), with patch_sha256. The tool reads only that directory, never through a symlink or a hard link, refuses a file whose SHA-256 differs, applies it as it applies patch, and removes it. Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-15 20:39:13 +00: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