Proposal: add a .gitallow allowlist for AI-generated repo artifacts

[Vijay431]

🏷️ Discussion Type

Product Feedback

Body

Problem

AI workflows can create lots of extra files in a repo: plans, temporary scripts, generated output, and helper notes. With .gitignore, it is easy for important files to be missed or for sensitive artifacts to be uploaded by mistake.

This matters because even experienced teams can accidentally commit or share files they did not intend to expose, including agent instructions or repo-specific config such as CLAUDE.md.

Proposal

Add a .gitallow allowlist that defines what is explicitly allowed to be tracked. Everything else would be skipped by default.

Why this helps

• Makes tracked files intentional
• Reduces noise from AI-generated artifacts
• Lowers the chance of accidentally exposing internal docs or agent instructions
• Helps large or fast-moving teams keep repo hygiene under control

Example risk

A file like CLAUDE.md or other internal guidance could be uploaded or committed unintentionally. An allowlist-based flow makes that less likely because only approved paths are considered valid.

Why this matters

Publicly reported incidents involving Apple’s Support app and Netflix’s iOS app accidentally shipping CLAUDE.md files show that this is a real workflow risk, not just a theory.

An allowlist-first approach would help prevent accidental exposure of internal agent instructions, repo guidance, and temporary AI artifacts.

Source links I used:

• Apple report discussion: Hacker News thread (https://news.ycombinator.com/item?id=47973378)
• Apple/X source referenced in that thread: X post (https://x.com/aaronp613/status/2049986504617820551)
• Netflix report: X post (https://x.com/aaronp613/status/2064541701012607181)

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