Replies: 1 comment 1 reply
-
🕒 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
Feature Request
Body
Current Workflow:
Currently, users must manually navigate to the Actions tab and trigger workflow_dispatch events. This manual process can be time-consuming and prone to errors when the workflows take multiple inputs
Request
I would like to request the ability to trigger GitHub Actions workflow_dispatch events via custom GET requests from the browser. This feature would enable users to initiate workflow executions programmatically from external systems or interfaces
Use Case:
As a developer, I often work with workflows that require multiple parameters. Manually populating these parameters for each execution is cumbersome and error-prone. With the ability to automatically populate workflow inputs via custom GET requests, this process would be streamlined, leading to improved efficiency and reduced errors. Additionally, having a final confirmation step would ensure user control and accountability.
Ideal Implementation:
The ideal implementation of this feature would allow for the automatic population of inputs based on the GET request parameters. Users would then be prompted for a final confirmation before triggering the workflow. Furthermore, the feature could support the addition of non-dynamic parameters as needed, providing flexibility and customization options.
Alternatives:
While alternatives such as using the
gh workflow run
feature or creating a wrapper script exist, they require additional setup and configuration, leading to increased complexity. The proposed feature would offer a more seamless and integrated solution for triggering workflow_dispatch events through the browserBeta Was this translation helpful? Give feedback.
All reactions