Native migration: system notes for new commits not properly migrated
For an example, see py-heptapod!15 (merged) it still has the Git commit SHAs (example 0ba321bd).
I believe the reason is that the regexp insists on the SHA to be a separate word with \b
whereas here's the system note for the example above:
"added 9 commits\n\n\u003cul\u003e\u003cli\u003e0ba321bd - git: split update_references() in two steps\u003c/li\u003e\u003cli\u003e02f655a7 - git: GitLab notification logic\u003c/li\u003e\u003cli\u003eeed3da6e - git: split the tests in two layers according to integration level\u003c/li\u003e\u003cli\u003e0fd02abf - git: special rules for topics not visible anymore\u003c/li\u003e\u003cli\u003edb52684f - Git: branches are closed by default\u003c/li\u003e\u003cli\u003e7e02e50b - git: making mandatory GitLab hooks raise Abort\u003c/li\u003e\u003cli\u003e95e57002 - git: restoring protection against prune of the default branch\u003c/li\u003e\u003cli\u003e0c61fc75 - git: translated functional test repushing on wild heads\u003c/li\u003e\u003cli\u003efae47f4c - gitlab hooks: stop returning None for no changes\u003c/li\u003e\u003c/ul\u003e\n\n[Compare with previous version](https://foss.heptapod.net/heptapod/py-heptapod/merge_requests/15/diffs?diff_id=4229\u0026start_sha=e47d9b23daf21f91b9669261c45e9893f3c3f099)"