Allow disabling Automatic Dependency Submission independently from Dependency Graph for private repositories

[McFcologne]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Other

Discussion Details

Problem

GitHub's "Automatic Dependency Submission" feature is automatically enabled for private repositories without user consent. This causes massive frustration for projects with private/internal dependencies that are inaccessible from GitHub Actions runners.

The Issue:

1. The feature automatically fails on every commit in private repos with internal dependencies
2. There is NO way to disable ONLY this workflow without also disabling Dependabot entirely
3. Users are forced to choose between: living with constant CI failures OR losing Dependabot security updates
4. This unwanted feature has already cost our team considerable time and effort

Requested Solution

Either:

• Disable "Automatic Dependency Submission" by default for private repositories, OR
• Provide independent toggles for:
  • Dependency Graph
  • Dependabot Alerts
  • Automatic Dependency Submission

So users can disable only what they don't need without sacrificing security features.

Context

This is particularly critical for enterprise environments with private artifact repositories that GitHub Actions cannot access. The forced activation of this feature without consent is poor UX and wastes developer time.

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