Purging of reported github issues in the repository #208928
Replies: 2 comments 2 replies
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
@Kotambail-Hegde the issues are most likely hidden, not deleted, and only GitHub Support can restore them. When an account is deleted normally, the issues and comments it created in other people's repos stay and move to @ghost. Here they're gone, and the API returns Open a ticket at https://support.github.com with the repo and a few of the missing issue numbers, and ask for the issues to be restored or exported. Docs:
If this solves it, please mark it as the answer so others can find it. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
Body
This is w.r.t the Issues reported in https://github.com/Kotambail-Hegde/Masquerade-Emulator/issues
As of last week, around ~100 issues were in open and another ~100 issues were in closed state for the above repo. Many of then were reported by user ScottNash042 but as of yesterday, I see that this account no longer exists (not sure why but none of my business) but all the issues reported by this user, the discussion regarding the debugs, the results etc. which I had done and was hosted in the description of the issues are all lost now. For some reason, the all the issues reported by the above said user also seems to be purged as well. This is a huge blow to the lot of hours of debug done by developers which we were hoping to be documented in these Issues.
We can stop the user from creating more issues but should not have purged such important debug details. Even though the issue was created by the above said user, It had contribution from other developers on Root Causing or Feature Design. Can you please look into this and help in restoring at least these data temporarily at least if not permanent so that it can be stored in a separate safe space.
All reactions