Plan the repository folder rename while preserving Codex and Claude Code history

Aperta
#62 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à
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva

Direzione di ricerca

This is planning work, not a code change: start with the prerequisite investigation in issue #61 and the existing rename request in issue #7. Inventory the local paths that Codex, Claude Code, installed skills, Git remotes and linked worktrees use for /Users/jetienne/webwork/coding_agent_plugin. Done means a reviewed plan with backups, rollback and verification checks, and no real folder or session storage changed.

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

Descrizione

Purpose

Apply the Codex and Claude Code folder-history investigation to the planned rename from coding_agent_plugin to coding_agent_plugins.

The existing rename request includes renaming the local folder. Jérôme has already experienced conversation-history problems after a folder change elsewhere, so the local-folder step needs an evidence-based plan before execution.

Prerequisite investigation

Use the documented procedures and live validation results from this investigation:

Existing rename request

Coordinate with the existing request rather than duplicate the repository rename implementation:

Work to do

  1. Separate the GitHub repository rename from the optional local-folder rename. The GitHub repository and local folder can have different names.
  2. Inventory the local paths used by Codex, Claude Code, installed skills, Git remotes, linked worktrees, and project configuration that would be affected by the folder change.
  3. Use the investigation results to propose either keeping /Users/jetienne/webwork/coding_agent_plugin unchanged or migrating to /Users/jetienne/webwork/coding_agent_plugins with a tested conversation-recovery procedure.
  4. Present the exact affected paths, migration steps, backups, rollback procedure, and verification checks for review before changing the real folder or session storage.
  5. Update the existing rename request to reflect the accepted plan. Distinguish repository URLs and published installation examples from existing local paths that must remain valid.

Acceptance criteria

  • The local-folder decision is supported by results from the actual interfaces and installed versions Jérôme uses.
  • Existing conversations remain discoverable and resume with their history and the intended working directory after restart, if a local-folder migration is chosen.
  • Other affected configuration and linked worktrees are accounted for; successful session recovery alone does not establish complete migration.
  • Keeping the current local folder is an explicit valid option if migration cannot be demonstrated reliably.
  • Report separately what was investigated, approved, renamed on GitHub, updated locally, and verified. Creating this issue does not execute any rename.
Lingua principale
Nessun dato sulla lingua
Stelle
1
Fork
0
Merge medio
7m
PR unite (30g)
17

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 jeromeetienne/coding_agent_plugin

Tutte le issue di jeromeetienne/coding_agent_plugin

Issue simili

Altre issue su DevTools

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.