Migration Required: Moving Open PRs from test-plans → unified-testing

[seetadev]

Dear contributors,

As part of a broader architectural decision within the libp2p ecosystem, we are consolidating all interoperability and performance test plans into the new libp2p/unified-testing repository.

We now need to migrate all open and active PRs raised against the previous test suite structure from:

https://github.com/libp2p/test-plans

to:

https://github.com/libp2p/unified-testing

This transition enables the unified-testing repository to serve as the canonical test bed for interoperability, benchmarking, and ongoing research & development initiatives within libp2p.

We deeply appreciate your continued contributions and sustained engagement with the ecosystem. The following PRs must now be rebased and moved.

---

📌 PRs That Need Migration

Please rebase and migrate your PRs accordingly:

🔹 dotnet / perf

• @K-21 – dotnet-perf PR
  fix(dotnet-perf): fix dialer bug affecting benchmark runs test-plans#831

🔹 leanp2p

• @bismuth01 – leanp2p transport interop
  Added leanp2p transport interop test-plans#830

🔹 browser fixes

• @asmit27rai – browser fix PR
  fix: browser tests failing because containers can't find Redis test-plans#814

🔹 py-libp2p hole punching

• @parth-soni07 – hole-punch PR
  feat(hole-punch): add py-libp2p v0.5 test-plans#813

🔹 python perf (WIP)

• @acul71 – PR
  wip: python perf test-plans#808

• @acul71 – PR
  Bump go test-plans#801

• @acul71 – PR
  Fix/enable debug in rust v0.56 test-plans#797

🔹 js-libp2p

• @Keerthivasan-Venkitajalam – js-libp2p PR
  feat: Add js-libp2p Echo Protocol Interoperability Tests test-plans#800

🔹 go holepunch interop

• @jpserrat – go holepunch interop
  Go holepunch interop with 0 46 test-plans#777

🔹 WebRTC interop

• @asmit27rai – WebRTC interop PR
  Webrtc Interop Added test-plans#756

---

🛠 Migration Procedure (Required – Preserves Commit History)

⚠️ Important: Do not use git diff -U. That approach collapses commits and removes commit history.

We must preserve commit structure and authorship using git format-patch and git am.

---

1️⃣ Checkout the existing PR branch

git clone https://github.com/libp2p/test-plans.git
cd test-plans
git fetch origin pull/PR_NUMBER/head:pr-branch-name
git checkout pr-branch-name

---

2️⃣ Export commits as a patch series (preserves history)

Identify the commit where your branch diverged from main (<since>), then run:

git format-patch <since>..HEAD --stdout > ../pr-1234.mbox

This exports each commit in order into a mailbox file while preserving authorship and commit messages.

---

3️⃣ Apply commits to unified-testing

git clone https://github.com/<your-fork>/unified-testing.git
cd unified-testing
git checkout -b pr-branch-name
cat ../pr-1234.mbox | git am

This replays the commits sequentially in the new repository.

---

4️⃣ Resolve conflicts (if any)

If git am pauses due to conflicts:

# resolve conflicts manually
git add .
git am --continue

If needed:

git am --abort

---

5️⃣ Push the migrated branch

git push origin pr-branch-name

---

6️⃣ Open a new PR

Submit a new PR to:

https://github.com/libp2p/unified-testing

Please reference the original PR in the description and link back for historical context.

---

Important Notes

• Do not force-push over old PR branches.
• Preserve commit history using the method above.
• Clearly reference the original PR in your new submission.
• Once migration is complete and validated, the old PR may be closed.

If anyone faces rebase or patch conflicts, please comment below and tag:

@dhuseby
@acul71
@seetadev

CC: @johannamoran

Let’s complete this migration carefully and smoothly for the libp2p ecosystem 🚀

[dhuseby]

@seetadev if people use git diff -U > ../pr-1111.patch it wipes out commit history. The instruction I gave you were incorrect. The correct approach is to use the command git format-patch <since>..HEAD --stdout > ../pr-1234.mbox and then to apply it in the new repo use cat ../pr-1234.mbox | git am. That will handle exporting each commit as a separate patch and then applying them in the same order with git am.

[seetadev]

@dhuseby : Hi Dave. Thank you so much for sharing this correction and feedback. Appreciate it.

Indeed, using git diff -U would collapse the commits and lose the original history structure.

Wish to share that I have now updated the migration instructions to use:

git format-patch <since>..HEAD --stdout > ../pr-1234.mbox
cat ../pr-1234.mbox | git am

This preserves commit ordering, authorship, and individual commit messages as intended.