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

未关闭
#62 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
12/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
没有语言数据
星标
1
派生
0
平均合并
7 分钟
30 天内合并 PR
17

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

jeromeetienne/coding_agent_plugin 的其他 Issue

查看 jeromeetienne/coding_agent_plugin 的全部 Issue

相似的 Issue

更多 DevTools Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。