In general, the pitfalls are the same as with the `mq` extension itself, and the justification for mutable history and the `evolve` and `topics` extensions. As it adds and removes commits all the time, you _may_ run into issues where a commit existed and was pushed/converted to Git, but is now gone.
Setting `mq.secret=yes` as suggested in the configuration is likely to help; in this case, you won't accidentally push the commits to Git — or Mercurial for that matter. _If_ you run into issues, a simple `hg git-cleanup` ought to resolve them, as it removes any mapping between Mercurial and Git that is now invalid, triggering a future reconversion.
But anyway, I'd suggest looking into `topics` and `evolve`; personally, I haven't used `mq` in several years — probably more than a decade 🙂
--
Dan Villiom Podlaski Christiansen
dan...@gmail.com —
+45 2728 9771