Commit graph

7 commits

Author SHA1 Message Date
ZTatman
d192fe8f4d fix(web): secure Forgejo requests and pin picker branch tips 2026-11-20 11:26:01 -05:00
ZTatman
c39385546e fix(forgejo): encode repository paths and branch refs 2026-11-20 10:47:38 -05:00
ZTatman
9d0e0b481a feat(repositories): extract routes and paginate owned listings 2026-10-16 15:07:51 -04:00
ZTatman
394e68abeb chore: just some formatting cleanup 2026-10-07 14:00:44 -04:00
ZTatman
984b382758 fix(forgejo): query commits by sha and normalize Commit payload
Forgejo's commits endpoint filters on `sha`, not `branch`. Sending
`?branch=<name>` was silently ignored and the API returned the default
branch's commits for every ref, so branch resolution appeared to work
while always yielding the same list.

Rename the parameter to `ref` (a branch, tag, or sha) and send it as
`sha`, documenting that the slot name is Forgejo's choice while the value
is a caller-supplied git ref.

The flat commits payload is GitHub-shaped (`sha`, `commit.message`,
`html_url`, `created`) while the nested branch commit uses `id`,
`message`, `url`, and `timestamp`. Give each Commit field an
AliasChoices/AliasPath covering both shapes so one model serves the
/branches and /commits endpoints, then map commits through it instead of
returning raw dicts under a `list[Commit]` annotation.

Also annotate get_branches' limit/page to match get_commits.
2026-10-05 15:45:22 -04:00
ZTatman
f00c25b7a0 feat(links): add repository and branch listing with Forgejo token dependency 2026-10-01 16:51:03 -04:00
ZTatman
3c3f47d20e refactor(web): rename config module to settings, add shared Forgejo API client 2026-10-01 16:51:00 -04:00