Preserve local transport identity docs through the reference content migration

Aperta
#792 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

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

Direzione di ricerca

Read the final owning source copies changed by documentation#788 and the companion associated with harper#3755; the payload does not name their file paths. Check that the local identity, migration, token, refresh-token, and session details and the CLI, MQTT, option-summary, and operation links are preserved, along with the 5.4 release note. Done means the companion content is present in the owning sources in the correct migration order, while the application-guide correction remains in learn/.

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

Descrizione

content
Documentation area

Current v5 reference and the 5.4 release notes.

Requested follow-up

Preserve the local transport identity documentation companion to harper#3755 through documentation#788, which moves current reference content into the product repositories.

Check the final owning source copies for the built-in local identity, reserved username and existing-user migration, credential-free token selection and 409 response, refresh-token replacement, and session isolation. Preserve the CLI, MQTT, option-summary and operation cross-links, plus the 5.4 release-note entry. The application-guide correction stays in learn/ here.

This is merge-order coordination, not a runtime defect. If the companion lands before #788, include its edits in the migration snapshot. If the migration lands first, carry them into the owning content sources before publishing the companion.

Review-Deferral: 877a0b2b077630ea severity=none category=documentation

Priority: P3. This is a bounded coordination task for an open migration, with no released runtime failure or identified customer block. Effort: Low. No existing content epic specifically owns this migration; no release milestone is committed for this tracking task.

🤖 Generated by OpenAI Codex; posted via @kriszyp.

Lingua principale
MDX
Stelle
9
Fork
9
Merge medio
5g 5h
PR unite (30g)
48

Preparare l'ambiente

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 HarperFast/documentation

Tutte le issue di HarperFast/documentation

Issue simili

Altre issue su Documentation

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.