Is it possible to manually force an action workflow to be re-run?

Lack of ability to rerun the workflow manually is a real showstopper for us. We would also like to have the ability to configure environment variables and branch while starting the workflow.

13 Likes

Manually rerunning an action is really needed. In addition I also would like to manually run a specific workflow; i.e. I would like to test a scheduled workflow before its scheduled run.

26 Likes

+1 for this. Sometimes there are errors (e.g. due to temporary upstream outages) when things run on a schedule, and being able to just click a button to re-run would be ideal.

Thanks for listening!

20 Likes

+1, manually restarting a workflow is currently the feature I miss the most.

I my case it would be even better if I could start a workflow on push to *other* repositories (for instance rebuild a top-level project when dependencies have changed).

7 Likes

+1
IMO, this is really a must feature for any CI service.

8 Likes

Hi all, I’m not entirely sure if this is appropriate or not to self promote here, but my buddy and I built an extremely basic MVP for handling this exact situation, because we wanted this feature as well:

https://www.actionspanel.app

We built it as fast as we could so it’s still very quirky, but we’d love feedback. There’s a contact email on that landing page.

1 Like

Its very hard to survive without this. Please, remove the condition to show the “rerun checks” only when the workflow failed.

11 Likes

Just fleshing out my workflow and got a lot of

dummy commit to trigger CI/CD workflow

commit messages in my repo so far :smiley:

It is very much required.

2 Likes

Is there any update on this feature request.

2 Likes

Yes, this would actualy be helpful! Simply remove the condition of failed.
I found this blog post which creates a workaround for manually triggering the workflow through a curl request using the API:

https://goobar.io/2019/12/07/manually-trigger-a-github-actions-workflow/

Could you please add me and my group to this feature request?

Today’s github outage meant that a few of our Actions runs didn’t trigger, and now I am forced to manually delete and re-apply the commits so they trigger properly.

2 Likes

Solution that works for me: To re-run a successful commit, push that commit onto a new branch or add a new tag.

1 Like

I second to remove the conditional re-run. In the meantime I have added a Github Action for a manual rerun that I trigger from Postman. It is a quick setup and works great. I have the steps outlined here https://medium.com/@christinavhastenrath/how-to-run-github-actions-manually-afebbe77d325 

1 Like

Said no successful pipeline service ever. Absolutely necessary in real world use. Showstopper. Prime example are those who could not run jobs because GitHub went down.

Forcing a commit is not a reasonable solution unless it’s stated that this feature is coming, and only then is it an acceptable workaround.

+1

We are migrating from GitLab to GitHub and I really really miss the feature to trigger the CI/CD pipeline manually. A “re-run” button shouldn’t be too hard to implement, either :wink:

+1

Trying to move from CircleCI to the Github Actions and really miss the ability to re-run the workflow instead of creating a dummy commit.

There is a re-run button:

Yes, you can re-run jobs, but what about if you want to create a workflow that you want to run on-demand?

I had success using the workflow_dispatch command using GitHub’s REST API to manually run GitHub Action workflows. Also, if you have a workflow that is triggered by the workflow_dispatch event, you can manually trigger it from the UI.

However, in my case, I needed something extra: which is the ability to re-run, from the command line, a workflow that was triggered by a pull_request event. Re-running it from the UI is possible as per @maxceem comment.

I tried using the POST /repos/{owner}/{repo}/actions/runs/{run_id}/rerun endpoint (https://docs.github.com/en/rest/reference/actions#re-run-a-workflow), but this endpoint does not support re-running a workflow that ended up successful.

This is a real show-stopper for me. Any ideas on why is that not supported? Are there plans to remove this restriction?