Reduce the amount of comments after parquet conversion
See https://huggingface.co/datasets/open-source-metrics/datasets-dependents/discussions/1#6537d488b33b913282d076de

> Would it make sense to just update the original message to add the different revisions that have been converted?

> I agree that editing original might be better. Translating this same situation to GitHub, I would not be happy with a bot that pings for every single commit. For example, the doc-builder bot does not write a comment for every commit in a PR, it just does a single comment and link will work. I don't think most users will want to get a new notification for every single commit. We can also not silence notifications at a repo level, so as a user i would be inclined to silence the whole org.

Let's just create a discussion that points to the refs/convert/parquet page, and ignore if a discussion already exists.
Reduce the amount of comments after parquet conversion: See https://huggingface.co/datasets/open-source-metrics/datasets-dependents/discussions/1#6537d488b33b913282d076de

> Would it make sense to just update the original message to add the different revisions that have been converted?

> I agree that editing original might be better. Translating this same situation to GitHub, I would not be happy with a bot that pings for every single commit. For example, the doc-builder bot does not write a comment for every commit in a PR, it just does a single comment and link will work. I don't think most users will want to get a new notification for every single commit. We can also not silence notifications at a repo level, so as a user i would be inclined to silence the whole org.

Let's just create a discussion that points to the refs/convert/parquet page, and ignore if a discussion already exists.