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

Ouverte
#62 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
12/100
Type d'issue
Refactorisation
Clarté
Plutôt claire
Activité
Active

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
Aucune donnée de langage
Étoiles
1
Forks
0
Merge moyen
7 min
PR mergées (30 j)
17

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de jeromeetienne/coding_agent_plugin

Toutes les issues de jeromeetienne/coding_agent_plugin

Issues similaires

Plus d'issues DevTools

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.