There should be a way for installations & FGTs to automatically have access to repositories they create

[xmo-odoo]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

API

Body

This is an annoying limitation of apps / fgts when dealing with automated workflows encompassing entire repositories, especially when trying to not over-allow / limit accesses: if not willing to grant the token full access to your account (so using repository_selection: selection mode), the token can create repositories (if admin:write) but then can't see / manipulate those repositories.

With apps it's possible to mitigate the issue by having two access levels: PUT /user/installations/{installation_id}/repositories/{repository_id} allows adding a repository to an installation so you can mess around with two different applications / tokens, or use per-installation-token restrictions to handle the situation, however that I can tell there is no such workaround for FGTs.

I think the fine-grained accesses / repository management should gain the following:

• if admin:write and repository_selection: selection, there should be a setting to automatically add repositories created by the installation / token to the selected repositories of that installation / token.

• An empty list of repositories should be allowed, especially if the token has the above. Having a warning box or a confirmation dialog is an option but an installation or token initially having access to no repository is not, strictly speaking, an error, and should not be forbidden.

  Hell, you can create a repository, create a token with access to just that repository, then delete the repository, and github's fine with that, you just get a token with access to no repos (until you try to update the token without adding a new repository to the empty list)

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