Allow configuring the details included in the comment

[gziolo]

Problem

See #21 (comment).

This is how part of the comment looks like today:

Feature Request

Would it be possible to make this configurable? While Core SVN makes perfect sense in WordPress develop, the GitHub Merge isn't that useful. Then, when contributing to Gutenberg, it was exactly the other way around. So, while the default could be as is, what if you could pass the setting when defining the GitHub workflow?

svnProps: true
gitCoAuthored: true

Workaround

No response

Repository

No response

[desrosj]

Thanks @gziolo!

I think this is reasonable. But, there's one scenario that comes to mind, though.

In WordPress/wordpress-develop, it's not uncommon for change suggestions in a PR to be copied over into a Gutenberg one. In that scenario, would it be helpful for the maintainer to have the GitHub-flavored list in order to include it in the Gutenberg merge?

Maybe we could add the ability to tell props bot to include both formats somehow. Maybe a props-bot-both label or something?

[gziolo]

In WordPress/wordpress-develop, it's not uncommon for change suggestions in a PR to be copied over into a Gutenberg one.

I didn't consider that scenario. Interesting. Maybe it's best to keep both for now and see whether it creates too much noise.

[noisysocks]

Didn't see this issue before opening #47.

I think it's currently far too noisy having both lists. At the very least we could collapse the non-relevant one behind a <detail>.

[noisysocks]

In WordPress/wordpress-develop, it's not uncommon for change suggestions in a PR to be copied over into a Gutenberg one. In that scenario, would it be helpful for the maintainer to have the GitHub-flavored list in order to include it in the Gutenberg merge?

I think you're over-optimising for an edge case here 😀 It's much much much more common (~20 new PRs are opened in Gutenberg every day) that you don't want this extra information than that you do want it.