Repository navigation
Clarify API key registration fields - #5585
Merged
obenland merged 1 commit intoAug 26, 2026
Merged
Conversation
Contributor
Author
|
The red CI on this PR is unrelated to the API documentation change. I temporarily pushed the build/lint fixes from #5602 onto this branch so those parts of CI could run; the affected Docker build and lint jobs are now passing. The remaining failures are the same pre-existing issue described in #5602: the Django check and API/ingestion-server test jobs fail during the Load Docker images step, likely from the |
ekamran
force-pushed
the
sftq/clarify-api-key-registration-fields
branch
from
August 26, 2026 05:14
7b126f3 to
4a919ef
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #1803