• she/her

Principal engineer at Mercury. I've authored the Dhall configuration language, the Haskell for all blog, and countless packages and keynote presentations.

I'm a midwife to the hidden beauty in everything.

💖 @wiredaemon


discord
Gabriella439
discord server
discord.gg/XS5ZDZ8nnp
location
bay area
private page
cohost.org/newmoon

So at Mercury we ran into a significant UX issue with GitHub where if you use GitHub's support for concurrency groups, like this:

concurrency:
  group: foo

… then your commit timeline is littered with a bunch of red ❌s from cancelled runs (since concurrency groups will cancel jobs to make sure that at most one job runs at a time). This can make it much harder to identify failed runs and there are at least two open issues related to this problem:

This is something that GitHub should fix on their own end, but in the interim we open sourced a GitHub action that works around this problem by clearing cancelled builds from the workflow's history. This leads to a much cleaner commit timeline where red ❌s are only relevant build failures.


You must log in to comment.