Repository navigation
[Automated] Draft docs (agentgateway): ui: save every editor through useMergedEdits (+3 related) - #1436
Open
github-actions[bot] wants to merge 1 commit into
Open
[Automated] Draft docs (agentgateway): ui: save every editor through useMergedEdits (+3 related)#1436github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
…useMergedEdits (+3 related) Drafts-Commit: 094f484 Signed-off-by: GitHub Action <action@github.com>
Deploying agentproxy with
|
| Latest commit: |
4bfa37e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1f2e3ceb.agentproxy.pages.dev |
| Branch Preview URL: | https://pr-tracker-draft-agentgatewa-vvem.agentproxy.pages.dev |
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.
Rendered output was not compared with the base build: the site does not build at the base commit ed3fb85, so rendering outside the declared versions is unchecked.
Feature clusters
These pull requests document one feature between them:
content/docs/standalone/latest/documentation/llm/playground.md, the only page a code-path rule names for one of them, so separate pull requests would conflict; the same author merged both within 24 hours, they change the same source file, and both are drafted intocontent/docs/standalone/latest/documentation/llm/playground.md, so this looks like one change split across pull requests and separate drafts would conflictKept apart on purpose. Merging wrongly produces a guide that documents two things and explains neither, so these are reported for a person to merge rather than grouped automatically:
content/docs/standalone/latest/documentation/llm/playground.mdas a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land therecontent/docs/standalone/latest/documentation/llm/playground.mdas a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land therecontent/docs/standalone/latest/documentation/llm/playground.mdas a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land therecontent/docs/standalone/latest/documentation/llm/playground.mdas a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land therecontent/docs/standalone/latest/documentation/llm/playground.mdas a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land therecontent/docs/standalone/latest/documentation/llm/playground.mdas a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land therecontent/docs/standalone/latest/documentation/llm/playground.mdas a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land therecontent/docs/standalone/latest/documentation/llm/playground.mdas a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land thereDraft a documentation change
agentgateway/agentgateway#4008 — ui: save every editor through useMergedEdits
agentgateway/website--validate-onlyafter drafting, and commands are unrunagentgateway/agentgateway#4013 — ui: mark required fields on the remaining forms; raw mode for keys
agentgateway/website--validate-onlyafter drafting, and commands are unrunagentgateway/agentgateway#4014 — ui: report all OIDC required fields on the first save
agentgateway/website--validate-onlyafter drafting, and commands are unrunagentgateway/agentgateway#4034 — ui: properly show schema help on all dropdowns
agentgateway/websiteA declared version this draft does not reach
This pull request is planned for more than one documentation version,
and nothing in the diff publishes to:
kubernetes/latestkubernetes/mainA file under
assets/reaches a version tree only where a page in thattree reuses it, so editing a shared asset does not by itself cover every
mode a product ships. Either that version still needs writing, or the
change genuinely does not apply there and the reason belongs in this body.
Draft branch:
pr-tracker-draft-agentgateway-4008-plus3Important
The test suite has not run on this pull request. It was opened by
github-actions[bot], and GitHub does not start workflows for pull requests opened with the repository's own token. Doc tests, link checking and the static checks are held asaction_requireduntil somebody presses Approve and run on the Checks tab. Cloudflare Pages and DCO are GitHub Apps rather than Actions, so those two do run on their own.Please approve the checks before reviewing the content: an absence of failures here means the tests have not run, not that they passed.