Philipp Daun

@speniti Are there plans for tackling this issue? Currently, the plugin has become unusable for any project with a custom public path. If the two suggested fixes above won't work,...

[I've published a fork of this library to npm](https://www.npmjs.com/package/laravel-mix-workbox-extension) that fixes the issue with broken outputs paths of async chunks.

@jacksleight This looks fantastic! I've been dreaming about this exact feature, just for asset fields. Do you see some sort of overlap between such a feature and the additions in...

@jacksleight Nice! I'll wait until this one gets merged then, and see what I can re-use if/when I give it a try.

Hi :) Not a big fan of having the numbers everywhere. I'd rather have an `open-sections` parameter or so defaulting to`['failed']` as now which can be set to `['failed', 'skipped']`...

Hi! No, this isn't currently supported, I'm afraid. It would involve two distinct steps I think: 1. Get the playwright report data, which would be somewhat difficult from outside the...

@awolfson2 Okay, that sounds doable. How would I give you access? PRs are open I think, but let me know if it needs anything else!

Nice, that way of using it looks fine. I'm not sure I'll get to it very quickly. Appreciate a helping hand in the form of a PR, otherwise I'll get...

Thanks @darmbrust, this is released as version 3.10. I've renamed the input `pr-number` for clarity. This is how it would look for this action: ```yaml - uses: jwalton/gh-find-current-pr@v1 id: pr...

Sounds good! I wouldn't want it in my report comments, but I'll happily take a look at a PR putting this behind a descriptive flag.