Will user-attachments/assets get deleted if a user, repo, etc. gets deleted?

[lwcorp]

Select Topic Area

Question

Body

When you upload an attachment (like an image), the resulting URL structure looks like https://github.com/user-attachments/assets/unique_id, which suggests the attachment is associated with a GitHub user account, not a specific repository, issue, pull request, etc. But if so, what happens if that user gets completely deleted? Do the attachments still remain in that case?

The Attaching files' doc doesn't mention the possibility of attachments ever getting lost. Then again it links to an outdated doc about the structure of anonymized URLs.
Meanwhile, the User deletion's doc mentions nothing about attachments.
Other related sources: [1], [2].
Proof of concept - here's a screenshot created from a now deleted username! But I still like to know officially - will it be eventually deleted?

[CloneOfAlex]

[boehs]

Chatgippity ahh answer

[lwcorp]

I assume that explains the complaint:

1. I've explicitly given the URL structure and noted GitHub's doc links to an outdated doc. So what did your AI do? It just completely ignored me and quoted the obsolete URL anyway, which from the get go suggested it won't solve the problem.
2. It gave 2 clashing points with with a Gibberish reference to the first of which.
3. It explained the downsides of never deleting such attachment, what does it have to do with the question on hand? I know the downsides or I wouldn't have asked this question in the first place.
4. It suggested to reach support, while this forum is where to reach support.

So basically it just flooded this thread with unhelpful text. It also doesn't give me credit by assuming I didn't think to check with AI myself before posting here.

While I appreciate the gesture and I use AI as my helper too, please - even for your own benefit, always check if its output actually solves the problem or at least doesn't add babble.

[boehs]

@lwcorp You phrased that so elegantly. People shouldn’t give AI answers unless they know enough about the subject matter to verify its accuracy and ensure only the relevant bits are shown.

another gripe: all we wanted was a link to the GitHub docs giving some explicit answer about retention policies. The bot didn’t provide it, just made up a lot of junk. Therefore it hallucinated its answer that retention is unlimited. This may very well be the case, but it could also be wrong. It lied by saying it knew something it didn’t

[v-mecodeatlas]

Hey @lwcorp 👋
We're reviewing some older unanswered discussions, and I know it's been a while - just wanted to check in and see if you were able to get this resolved. If not, feel free to share an update so other community members can jump in and help.

[lwcorp]

Hi, there was simply never any any answer to this discussion, just one that was blanked out (feel free to delete it, I guess) and comments that explained why it didn't answer the discussion.

[shadikhasan]

Yes. User attachments and uploaded assets are deleted when the user or repo they belong to is deleted.

[lwcorp]

Did you see the proof of concept in the OP that proves they're not deleted?
The question is when - if at all - they'll ever be deleted.

[ghostinhershell]

Hey @lwcorp!

Thanks so much for reaching out in the Community! Attachments uploaded to GitHub issues, pull requests, or comments are hosted at anonymized URLs and are publicly accessible. However, GitHub currently does not provide a direct way for users to delete these attachments themselves once uploaded.

To request the permanent deletion of an attachment, you will need to contact GitHub Support directly. You can do this by submitting a support ticket through the GitHub Support contact form. In your request, include the following details:

• The anonymized URL of the attachment you want to delete.
• A brief explanation of why the attachment needs to be deleted.

Note that, for privacy and security reasons, only uploader of the attachment can authorize the deletion of the attachment. Let me know if you need further clarification or assistance!

[lwcorp]

Thank you, but this doesn't answer the question. In fact, if a user gets deleted he won't be able to use that form.

[ghostinhershell]

@lwcorp you can still submit a support ticket without logging in here: https://help.github.com/request/landing. Click the "Can't sign in or don't have an account?" link and, from there, select the "No account: I don't have a GitHub account" option.

[lwcorp]

While that's true, the subjects available there are a very short list, none of which is remotely related to issues likes attachments:

[ebndev]

Hi @lwcorp, as we are unable to fully answer your question: will it be eventually deleted?, I've gone ahead and updated this discussion to have the Product Feedback label so that our internal teams are able to track it and update the documentation. There is no guarantee each post will get a response from a product leader.

Is there anything else in the current documentation that you'd like to clarify?

Thank you for contributing and continuing to support other users in the GitHub Community Discussions.

[bahatijacklee]

This is a good question, and I don't think the current documentation clearly answers it.

I wouldn't assume that the attachment is deleted just because the URL contains /user-attachments/, nor would I assume that it is guaranteed to remain after the uploader's account is deleted. The URL structure alone doesn't establish the attachment's retention policy.

Since the documentation on account deletion doesn't explicitly address user attachments, the safest answer would be to ask GitHub Support for clarification or request that the documentation be updated to specify what happens to existing attachments when their uploader's account is permanently deleted.

It would also be useful to know whether attachments referenced from issues, PRs, or discussions are treated differently from unattached files.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐