Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Restructure the PHP "Run a Worker" page to match the other SDKs

Aperta
  • Qualcosa non va?
#5,532 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
documentation

Direzione di ricerca

Read docs/develop/php/workers/run-worker-process.mdx alongside the equivalent Run a Worker pages for the other SDKs, and check the heading conventions in AGENTS.md. First confirm with the PHP SDK owners which sections and related pages apply, especially versioning, RoadRunner shutdown, Interceptors, and Serverless Workers. Done means the page has the applicable sections, preserves #run-a-dev-worker and #register-types, and follows the documented heading conventions.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

The PHP SDK's "Run a Worker" page (docs/develop/php/workers/run-worker-process.mdx) doesn't follow the structure the other SDKs use. This came up in review of #5480, which normalized the page's title and sidebar label but left the body as is.

The other seven SDKs share six sections on this page: Create and run a Worker, Register Workflows and Activities, Connect to Temporal Cloud, Configure Worker options, Run a versioned Worker, and Shut down a Worker. The PHP page has two headings, "How to run Worker Processes" and "How to register types". The Temporal Cloud connection, Worker options, and RoadRunner configuration content sits under those two headings without its own sections.

The PHP Workers section also has no Interceptors page, and no Serverless Workers page.

Proposed work

  • Restructure run-worker-process.mdx to use the same section headings as the other SDKs, keeping the existing explicit anchor IDs (#run-a-dev-worker, #register-types) so inbound links keep working.
  • Split out the existing Temporal Cloud (ServiceCredentials) and WorkerOptions content into their own sections.
  • Confirm with the PHP SDK owners whether the other SDKs' sections apply to PHP (Worker Versioning, graceful shutdown under RoadRunner) and write only the ones that do.
  • Confirm whether the PHP SDK has Interceptors and whether Serverless Workers is supported, and add or deliberately omit those pages.
  • Bring the page to the heading conventions in AGENTS.md (sentence case, task-oriented, infinitive verbs).

Related

  • #5480 (Workers section audit, where this was raised)
  • The code on this page is hand-written. Moving it to documentation-sdk-code-examples is tracked in #5533 so the two changes can land in either order.
Lingua principale
JavaScript
Stelle
175
Fork
333
Merge medio
1g 7h
PR unite (30g)
140

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di temporalio/documentation

Tutte le issue di temporalio/documentation

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.