| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Commitfests marked as draft are otherwise indistinguishable from regular ones in the API output, since they share the Open status.
There is currently no way to discover which commitfests exist. The needs_ci endpoint only returns the two or three currently relevant ones, and the patches endpoint requires a commitfest id you already know. API consumers are left enumerating ids until they get a 404, or scraping the HTML pages that already show this data. This returns every commitfest, closed and draft ones included, ordered by id. It deliberately does not use CommitFest.relevant_commitfests(), which has write side effects and can return unsaved objects.
|
Linter/formatting check is failing. Other than that this seems like a good addition. |
Sorry, something went wrong.
|
The linter/formatting failures are throughout the repo, it seems like ruff pulled in a new version with different defaults. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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:
{"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: