Git Large File Storage behavior should treat forks as first-class citizens

[wyattscarpenter]

Select Topic Area

Product Feedback

Body

https://docs.github.com/en/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage#pushing-large-files-to-forks helpfully tells us

Pushing large files to forks of a repository count against the parent repository's bandwidth and storage quotas, rather than the quotas of the fork owner.

You can push Git LFS objects to public forks if the repository network already has Git LFS objects or you have write access to the root of the repository network.

This is not how it should work. Instead, pushing large files to forks of a repository should count against the quotas of the fork owner.

I'm currently trying to push an LFS object to a repository of mine, and it won't let me, because my repository happens to be a fork, a property of my repository that I would like to remain true.

I get this message:

batch response: @wyattscarpenter can not upload new objects to public fork wyattscarpenter/unsong-book-fetcher

I don't think there's a way to get around this problem as of now (besides deleting and recreating the repo so that it's not a fork, which I don't really want to do). And yet, it seems like the behavior could be changed so that my goal would be possible.

Here are some examples of other people having problems with this:

• https://github.com/orgs/community/discussions/81372 " Trouble Pushing Files "

• can not upload new objects to public fork  git-lfs/git-lfs#1906 " can not upload new objects to public fork "

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