New release in progress <https://github.com/OpenHa...
# proj-agent
c
r
Need any extra hands? Mine are…. Open. 🫢
c
You're welcome to check it out, I think Simon is working on it, what I’d love to figure out is how to make the many many comments that end up on a release PR a little more visible or understandable… because failures can be missed šŸ¤” How do you think about a workflow that will always post LAST, and running on every comment… to say e.g. ā€œTHIS PR HAS FAILURESā€ šŸ˜…
OK probably a bad idea
But take a look - they become difficult to notice unless you are paying attention
r
Yes, it reads like a log and it would benefit from a pinned ā€œthings that need attentionā€ card that is persistent and updates on each workflow run/commit
nod 1
Anything reusable in the ecosystem that could fit that need?
c
Multiple workflows that post a single comment, as in, if there was a comment already they delete it and replace it
r
Yeah that would be super helpful for humans
s
@calm-artist-7206 woops I clicked on "Re-request" by mistake
np 1
r
Do yall use a db backend for maintaining the repos or is it all graphQL
c
graphql
r
There's got to be a way to make a release ontology that can be used to make a persistent highlight comment card
Without much extra engineering
Don't let me distract the release, I'll think on it
ty 1
s
seems like flaky tests are preventing the release? I'm heading out so I won't be able to fix this right now, maybe in a few hours! FYI @modern-fireman-99755 @calm-artist-7206
šŸ‘ 1