Actions became enabled automatically after transferring a fork to an organization #199004
Replies: 1 comment
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Other
Discussion Details
Description
I forked a public repository and never manually enabled GitHub Actions.
Later, I transferred the fork to an organization.
After the transfer, I started receiving GitHub emails about workflow failures. The workflows were clearly being executed, even though I had never intentionally enabled Actions before the transfer.
Expected behavior
GitHub Actions should remain disabled unless explicitly enabled by a repository administrator.
Actual behavior
After transferring the fork to an organization, workflows started running automatically and workflow failure notifications were sent by email.
Additional information
Is this expected behavior, or could this be a bug related to repository transfers and Actions settings?
Beta Was this translation helpful? Give feedback.
All reactions