tree 74d1ed9905034a3a41110995c6981ccfb4111284
parent c1b424c8b7304da5a5aa06599d7fd449822b15ab
author Geoffrey Martin-Noble <gcmn@google.com> 1684278883 -0700
committer GitHub <noreply@github.com> 1684278883 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkZA5jCRBK7hj4Ov3rIwAA/xQIABUNTHDpF3dPoVzf/LRu/0ha
 doWl8/0ZJyQx8HBy5pY4HJWkbVNj25NvNi3eTdagG7Wr1yYY1CFd6NAeBU+pPFma
 pJokOqB15ooaqyNqlZNXIZW4fBVkQYWR3aoWZdtSsSohOt9xEXrS6/Ng1vvPzdOD
 I0xU9saEY4EMmXn4J9I7EjRGFWiNHF8z6kUPmoI1cwgn00ejt0S5EchniNXCnlme
 LyuTLW8cAXYH9MOr6iKXD0zIgU9ntvq2u2A3NMeWAgizuw7/5ZCuVd0hx6sTLJMO
 RI2napiFY9iQfcrfxUkpfFU0cX+rstzqn7lY/1WWgfk9l/r8nuETUmNvVr5pL7I=
 =eAY4
 -----END PGP SIGNATURE-----
 

Make Discord notification link directly to workflow run (#13646)

This makes the title a URL that takes you to the thing you actually
want to see: the failing run. Currently the closest thing is the checks
page, which is super noisy for commits on main because all the stuff
running on `schedule` or `pull_request_target` run in the context of
the HEAD commit on main and apparently post all their checks there...

I tried also making the message less noisy in general, but it removed
too much context. If we want something different, we'll have to switch
to a different action: this one deliberately already has everything
formatted for you. Although really I'd love to figure out a way we can
use issues for CI failures. Discord kind of sucks for tracking.