Introduce commit_dispatch event

Please consider introducing commit_dispatch event, or add functionality to repository_dispatch event so that it can be triggered for desired commit.

I know that your logic is “but even though it triggers on master branch, you can modify this workflow to checkout desired commit sha” but this is huge limitation and makes our work much harder.

Imagine company that works on 20 projects, monorepos, with CI that is very advanced and modified constantly. And now imagine that on branch master you have dispatch workflows that are triggered externally, on demand:
update_server
update_rails_database_on_server
update_wordpress_database_on_server
update_tools_database_on_server
update_assets_on_server
update_pricings_on_server
… and so on…

And your task is to create new branch and change those workflows, well actually, 100 other developers create XX branches where they add, remove, tweak current workflows. If dispatch_workflow is triggered from master then those changes from branches are not available, and you would need to keep merging them to master or even just work on master (which is not available in many companies - security).

This feature allows creating Powerful Advanced Workflows and custom actions without making Dev life miserable trying to create hacks for that (hacks that are miserable too :<).

IMPORTANT:

  • This feature is present in GitLab and it is a fundament of our CI/CD, and while trying to move our company repos to Github Workflows we see that lack of this feature is very painful.

Similar topic:

2 Likes

:wave: @Evilweed – Thanks for this feedback! We’re always working to improve GitHub and the GitHub Support Community, and we consider every suggestion we receive.

Would you mind submitting this through our official product feedback form so that our product team can track your request? That’s the best place to share requests like these in consideration for future iterations of GitHub features.

@francisfuzz no problem - did that right now

1 Like