How to enable workflows after forking using API #39307
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hello folks,
By using github API, I created a fork from a private repository that contains Github Action workflows.
And I made a new tag and pushed it to the new forked repository and I expected that new Github Action got started.
But Github Action didn't start... Because Github Action is disabled by intention when the repo is created by forking.
As you can see below, I should click the green button to enable Github action.

But I need to make this process automatic...
So I tried to find how to enable Github Action of new forked repository, but I failed.
Is there any API that can help solve my problem..?
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions