Merge duplicate coprocessor documentation#8844
Conversation
|
@Copilot: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/ |
✅ Docs preview readyThe preview is ready to be viewed. View the preview File Changes 0 new, 3 changed, 1 removedBuild ID: 447bb25237479d60744560e0 URL: https://www.apollographql.com/docs/deploy-preview/447bb25237479d60744560e0 |
Co-authored-by: abernix <841294+abernix@users.noreply.github.com>
|
Linking this to #8384 where things ended up in the wrong place. |
|
@Copilot, please consider creating a changeset entry in |
pragl
left a comment
There was a problem hiding this comment.
A couple minor recommendations from our AI reviewer based on the style guide, which I copied in as suggestions. Otherwise, LGTM!
Co-authored-by: Parker <parker.ragland@apollographql.com>
|
@mergify backport main |
❌ Unable to backport: Mergify can't impersonate
|
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: abernix <841294+abernix@users.noreply.github.com> Co-authored-by: Jesse Rosenberger <git@jro.cc> Co-authored-by: Parker <parker.ragland@apollographql.com>
Description
Duplicate coprocessor documentation existed where only one file was linked in the sidebar:
docs/source/routing/customization/coprocessor/index.mdx(in sidebar)docs/source/routing/customization/coprocessor.mdx(not in sidebar)The orphaned file contained a unique "Per-stage coprocessor URLs" section showing how to override the global coprocessor URL per-stage.
Changes
coprocessor.mdxfileChecklist
Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.
Exceptions
Notes
Original prompt
This pull request was created from Copilot chat.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.
Footnotes
It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this. ↩
Configuration is an important part of many changes. Where applicable please try to document configuration examples. ↩
A lot of (if not most) features benefit from built-in observability and
debug-level logs. Please read this guidance on metrics best-practices. ↩Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions. ↩