openclaw - 💡(How to fix) Fix refactor: consolidate mega-merge files under mega/ directory [1 comments, 1 participants]

Fix Plan

To move the mega-merge tooling into a dedicated mega/ top-level directory, follow these steps:

1. Move files:

   • git mv scripts/mega-merge.ts mega/scripts/mega-merge.ts
   • git mv docs/mega-merge-history.json mega/docs/history.json
   • git mv docs/mega-merge-autoskip.json mega/docs/autoskip.json
   • git mv docs/mega-merge-report.json mega/docs/report.json
   • git mv docs/mega-merge-changelog.md mega/docs/changelog.md

2. Update hardcoded paths in mega-merge.ts: Replace occurrences of:

   • docs/mega-merge-history.json with mega/docs/history.json
   • docs/mega-merge-autoskip.json with mega/docs/autoskip.json
   • docs/mega-merge-report.json with mega/docs/report.json
   • docs/mega-merge-changelog.md with mega/docs/changelog.md

   Example:

   // Before
   const historyPath = 'docs/mega-merge-history.json';
   // After
   const historyPath = 'mega/docs/history.json';

3. Update .github/workflows/mega-merge.yml: Replace bun scripts/mega-merge.ts with bun mega/scripts/mega-merge.ts.

4. Update .gitignore: Replace docs/mega-merge-pr-cache.json with mega/docs/pr-cache.json.

5. Update README.md: Modify the key files table to reflect the new paths.

Verification

After completing these steps, verify that:

• The files have been moved correctly using git ls-tree -r --name-only HEAD
• The workflow runs successfully with the updated mega-merge.ts path
• The .gitignore entry is correctly ignoring the pr-cache.json file
• The README.md reflects the updated file paths

Extra Tips

• Make sure to commit each step separately for easier tracking and rollback if needed.
• Consider adding a test to ensure the mega-merge tooling works as expected after the move.