When an issue has unsupported markdown, manual workflow fails

[corentingiraud]

Describe the bug

Using the manual workflow, if an issue hase unsupported markdown, the whole workflow fails.

Steps to reproduce

1. Create an issue with supported markdown
2. Create another issue with unsupported markdown
3. Launch a manual workflow

Expected behavior

The job should synchronize all issues. Issues with unsupported markdown should have an empty body or an explicit error as a body.

Additional context

No response

[EndBug]

Hey, thanks for opening the issue!
I've just merged a fix that will prevent the action from failing when the first element is not supported: if an error is thrown, the body will just be blank.

I'm planning to add a way to better parse the body property and to fill the child page with actual blocks instead of just rich text. This is just a fix so that the action is usable in the meantime