How to change the text of Run Failed email notification?

Hi all. I’ve added a GitHub Actions to the CI workflow of my project, but unfortunatelly it doesn’t work when the pull request is sent via a Fork branch (it’s seems that this is an issue with lots of GitHub Actions!).

This doesn’t prevent the merge of the PR, but when the user who sent the PR receives a notification like this gets concerned, the user thinks that they did something wrong.

Run failed for cms/amussapvordel/axway-open-docs/apigtw_devguide/test-1 (d56c844)
Repository: Axway/axway-open-docs
Workflow: size-label
Duration: 27.0 seconds
Finished: 2020-03-13 15:45:06 UTC

Since I still didn’t find a better Action to replayce the ‘size-label’ one, as a workaround I’d like to know how to change the message on the notification to add some information to tell the user that they don’t need to worry about it.

@andreamussap - Hey there! It’s not possible to change the text of that email notification at this time. However, our product team is keen to hear this sort of feedback and we encourage you to share it with them here:

With respect to a workflow _not _triggering when the pull request is sent from a fork’s branch, could you share a specific instance of that with us here? I’d love to look into that and see what might be happening there. :eyes:

@francisfuzz thanks for repling to my question. If there’s no issue/ solution you can close this ticket.

I’ve sent the feedback as per your suggestion.

As for the GitHub Actions/Fork branch issue, please have a look at this -


> If there’s no issue/ solution you can close this ticket.

> I’ve sent the feedback as per your suggestion.

@andreamussap - Thanks for doing that! I’ll go ahead and mark this as the “accepted solution” given where we are. Also, thanks for sharing that topical reference around Actions and forks. I noticed one of my colleagues, ethomson, working on GitHub Actions replied to and acknowleged that topic. I know that other people are adding their input as well and while I can’t speak to any other new updates as of yet, we definitely recommend following our GitHub Blog’s Changelog for the latest updates:

Hope this helps!

1 Like