839

Thank you for your suggestion. It seems that there are cases where displaying all messages can be very long. We need to think about what specifications are good.

Thank you for your suggestion. It may take some time, but I would like to deal with it. If possible, you can send us a PR.

Thanks for the report. Could you please share a simple sample yaml? It would be great if we could do a check operation.

Wouldn't it be fixed by adding ` MATRIX_CONTEXT: ${{ toJson(matrix) }}` ? refs: https://action-slack.netlify.app/fields

I see. Maybe it's a pattern I'm not recognizing. Can you provide a minimal yaml that reproduces the problem?

Thank you. I will investigate based on this.

I see. I've certainly felt that too. I can't think of a very quick way to do it, but I'll try to think of a way.

Cache is also a good idea. But state management can be complicated, so I'm thinking of other ideas. My proposal needs to be narrowed down to the following notation. The...

`needs` specified job must be successful. In this case, no failure notification is given.

Oops, I was missing out. ```yaml needs: [put,other,job,ids,here] if: ${{ failure() }} ``` By writing `needs` and `if` together, can I wait until the job is finished and still run...