Skip to content

Adding additional patch fields, history endpoints. - #132

Open
kjrocker wants to merge 13 commits into
postgres:mainfrom
kjrocker:main
Open

kjrocker wants to merge 13 commits into
postgres:mainfrom
kjrocker:main

Conversation

@kjrocker

@kjrocker kjrocker commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

This is all serving up data that already existed. Adding the reviewers, committers, target version, tags, wiki/git links, and created/modified dates fills out the patches with all the fields on the page.

There's also a single-patch /patches/ endpoint, returning the same patch object as the commitfest listing with its threads included.

Then I added a per-patch /history endpoint to cover the history table we already have.

Finally, a global view into the history across all patches, which gives us the ability to see what's changed since a specific date. I went with cursor pagination, since this acts more like a feed than something you'd select individual pages from.

One pattern this introduces is a standard JSON 400 error envelope {error: '<message>' }, which /patches/ also uses for its 404. Right now our error handling has JSON endpoints returning HTML 404s and is pretty inconsistent throughout. I can polish that up, but I'd want to do it in a separate PR.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant