Consider gotestfmt to make test output in CI more readable about .goassets HOT 5 CLOSED

@daenney Yes please!

We also need to improve the commit message linter. It would save me so much time if it spit out a 'GitHub Actions Native' message. The users don't need to open up the action stdout.

from .goassets.

Crap, I accidentally pushed 0.7.0 tag which triggered stuff all over the place (the sync run broke eventually because it got rate limited).

So, on the bright side, test output is much more useful: https://github.com/pion/dtls/runs/6004489095?check_suite_focus=true#step:6:15

But, it does seem to actually cause code coverage issues pion/dtls#44 but idk why.

from .goassets.

It would save me so much time if it spit out a 'GitHub Actions Native' message.

I can look at this, but I'm having a seriously hard time Google'ing for what that would need to look like. Do you have any pointers to docs or something that explain how the output needs to be formatted? Or do we need to call some API instead?

from .goassets.

@daenney Are you still up to taking this task? Or would you mind if I take over?

from .goassets.

I just realized that the CI is already using gotestfmt:

I will close this issue and create a new one for the related issue regarding the commit message linter output which @Sean-Der raised.

from .goassets.