alexion/gitea-axi
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: alexion:5de30b1c74d28f20fe71c641207e711e50905e81
Branches Tags
alexion:main
..
compare: alexion:db2285b40d8fd9d0995202af49fd7f00721d01d3
Branches Tags
alexion:main

1 Commits
5de30b1c74 ... db2285b40d

Author SHA1 Message Date
alexion
db2285b40d docs: map Gitea web UI vs REST API parity gaps
All checks were successful
CI / test (pull_request) Successful in 58s
Details
CI / test (push) Successful in 54s
Details 
Nine capabilities the web UI exposes that the REST API does not, in the
issue/PR/review domain, analysed against go-gitea/gitea at e8befe0.

Each finding cites the web route, the service function its handler
reaches, the swagger evidence, upstream prior art, and a patch sketch.
Ranked by impact and tractability, with issue drafts for the five to
file first.

Also records that resolve/unresolve review conversations and threaded
reply endpoints already exist upstream, which supersedes the premises of
issues #38 and #39.
 2026-07-18 15:57:29 -04:00
1 changed files with 3 additions and 2 deletions
Expand all files Collapse all files

5
CLAUDE.md
View File

@@ -13,9 +13,10 @@ The benchmark arms invoke the **built `dist/main.js`** (the `gitea-axi` binary o
Run `npm run build` before any live `bench:run` if you want `src/` changes reflected; the bench does not run from source. Run `npm run build` before any live `bench:run` if you want `src/` changes reflected; the bench does not run from source.
Prefer this project's own CLI for pull requests — it is the tool being built, so opening its PRs with it is the dogfood path: Prefer this project's own CLI for pull requests — it is the tool being built, so opening its PRs with it is the dogfood path:
`npm run build && node dist/main.js pr create --login alexion --base main --head <branch> --title <text> --body-file <path>`. `npm run build && node dist/main.js pr create --login axi --base main --head <branch> --title <text> --body-file <path>`.
The login profile is named `axi`, not `alexion` — passing `--login alexion` fails with `VALIDATION_ERROR`.
It reuses the `tea` login profiles, so it needs no separate credentials. It reuses the `tea` login profiles, so it needs no separate credentials.
Fall back to `tea pr create --login alexion --base main --head <branch>` only for what gitea-axi cannot do yet; `tea pr` still lists PRs until `pr list` lands (task 0008). Fall back to `tea pr create --login axi --base main --head <branch>` only for what gitea-axi cannot do yet; `tea pr` still lists PRs until `pr list` lands (task 0008).
Task branches are merged into `main` on the remote, so the local `main` goes stale. Task branches are merged into `main` on the remote, so the local `main` goes stale.
Always `git fetch origin` and cut a task branch from `origin/main`, not from whatever local `main` happens to point at. Always `git fetch origin` and cut a task branch from `origin/main`, not from whatever local `main` happens to point at.