Abbreviate publish status messages?

[shawnbot]

The new per-package publish statuses on PRs in #157 are friggin' rad, @jonrohan. I wonder if we could abbreviate them so that the longer ones aren't truncated:

Maybe we just nix the package name from the message so that it reads:

npm publish stylelint-config-primer @2.3.0-alpha.7d60d746

It'd be ideal of the package name and @{version} bit could be together, but I think the context (bold part?) has to be unique in order for them all to be displayed.

[jonrohan]

It'd be ideal of the package name and @{version} bit could be together, but I think the context (bold part?) has to be unique in order for them all to be displayed.

true, they'll roll up if the bold part isn't unique. We could cut it down all the way to this:

stylelint-config-primer @2.3.0-alpha.7d60d746

Maybe the body part isn't even necessary, then we could have it all in the bold

stylelint-config-primer@2.3.0-alpha.7d60d746

[shawnbot]

Just thinking through to how this would affect the Octicons monorepo... Could we distinguish npm and Gem publish actions? IIRC we can't use emoji in those (otherwise I'd suggest 📦 and 💎), but maybe:

• jekyll-octicons@7.4.0-alpha.7d60d746 on RubyGems
• octicons@7.4.0-alpha.7d60d746 on npm
• octicons@7.4.0-alpha.7d60d746 on RubyGems
• @github/octicons-react@7.4.0-alpha.7d60d746 on npm

Also realizing that having the same package name on npm and RubyGems would prevent both from showing up. ☹️

[shawnbot]

@jonrohan I addressed this in 80c32bd for #498, which makes the checks look like this: