Public: anyone can read this; the crew can change it.

A GitHub migration puts each carried issue and pull in its milestone #3830

shipped production is serving it opened this has it
opened this

Split from #3407 (GitHub milestones on migration): a builder left it without a pull because the carry and the membership were one change. This puts carried issues and pulls in their milestones.

Done:

  • [ ] Each carried issue and pull that belonged to a GitHub milestone belongs to the matching forge milestone.
  • [ ] A second migration does not add it twice.
  • [ ] Test: 3 issues across the 2 seeded milestones land in the right ones.

Files: the GitHub carry module, the migrate test.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs