Ben Menesini

> Hi all, looks like Azure DevOps customers were not prepared for this change and while Actions customers need to only modify their pipelines to mostly switch `docker compose` from...

> sorry, what revert means? `docker compose` will now not work and we need to switch back to `docker-compose`? please don't 🙏🏼 I'd expect both to work after the revert;...

I agree - yargs is likely the right solution. I'm actually in the middle of solving a different challenge with this repo (evaluating live status of profiles instead of discrete...

I also encountered this today in a workflow that has many parallel jobs that independently authed with AWS successfully - just the one job failed. I suspect that something is...

Almost all our our trap cache is from our default branch, which we merge to more than 60 times a day on average. Even if this only ran on the...

Another possible approach might be to save the trap cache as an artifact, then pull the most recent artifact from the workflow run on the default branch when restoring the...

Ah, then the idea is to update the cache key to remain consistent and use the API to remove the old cache so the key can be updated? That should...

Thanks for the context! Completely understood about the spec, though I'm curious if you'd consider making the attribute optional and default to off? As for whether Jest passes the line...

@palmerj3 Would you mind re-opening this issue? I've created an internal ticket to open a PR for this feature and would like to use this issue to help track

> I am thinking this project would do better to move to nextjs I'm curious as to what you think this might improve or fix aside from adding another build...