You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 07e2bc6
Browse filesBrowse the repository at this point in the historyBrowse files
Add GET /api/v1/commitfests endpoint listing all commitfests (#114)
There's no way to discover which commitfests exist. `needs_ci` returns
only the two or three currently relevant ones, and
`/api/v1/commitfests/<cfid>/patches` requires a cfid.
This adds `GET /api/v1/commitfests` which returns every commitfest,
closed and draft ones included:
```json
{"commitfests": [{"id": 1, "name": "PG18-3", "status": "Closed", "draft": false,
"startdate": "2024-11-01", "enddate": "2024-11-30"}, ...]}
```
This data is all already available from `/commitfest_history` and
`/archive`, but those would need to be scraped, this makes the data
machine-readable.
Notes:
- Order by ID since start dates can tie and this gives us a stable
order.
- No pagination because it's a small dataset.
- I've exposed the 'draft' field through `CommitFest.to_json()`. This
does add the key to `needs_ci`. If we'd rather be strict about that
endpoint, I can build the dict inline in a new view instead.
0 commit comments