#59391

I guess trying to use the github model for discussions is perhaps the wrong model since it makes such simple
actions so difficult.
Maybe a better way to frame my question is, can I "supersede" my whole message with a new version of it
that becomes 'the current, main' version of it such that most users from now on will see,
if they don't bother to look into the history?
Is a discussion really part of the "repo" in the sense that it is versioned, branched, etc just like my source code?
If so, that's a lot of overhead!

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬