Need a webhook event for repository transferred in original organization

[steinybot]

Select Topic Area

Product Feedback

Body

I see that the repository webhook only sends the event when a repository is transferred to the destination organization:

Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the repository.transferred event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events.

This is a pretty serious limitation. The original organization gets all the events for that repository when it is created, renamed, edited, archived, unarchived, even deleted but there is no way no when it has been transferred? I don't understand the rationale for this seemingly intentional decision.

I have a GitHub App that listens for repository and custom_property_value events and will then list all our repositories and get the value of the Group property for each one. It then updates our organization's profile to list each repository under a collapsible section for each group. This is a pretty nice workaround for having no ability to group repositories. Without this, my organizations profile becomes out of date if someone transfers a repository to another organization.

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