Claas Augner

> Should we replace all four occurrences of `Web` on the page As clarified with @Rumyra, all occurences of `Web` on the Community page should be replaced with `web`.

Fixed via https://github.com/mdn/yari/pull/5532.

Our current plan is to actually move checks from flaws (build-time) to filecheck (on-demand) to reduce our build time, so we don't plan on doing the inverse (moving filecheck into...

> And of course this would be even better ^^^ @hamishwillee FYI Since September 2022 (https://github.com/mdn/content/pull/21009), `yarn filecheck` is actually run on images to be committed as part of the...

> Unfortunately, with the introduction of the `@mdn/bcd-utils-api` package, this is no longer possible, making local testing virtually impossible. @queengooborg Can you explain why `npx install-local` no longer works since...

> Well, there's one big reason why using BCD directly doesn't work: Yari depended on custom properties provided by BCD-utils transforms! I'm not sure I understand. Currently we fetch the...

I quickly looked into this and the "PR review companion" workflow seems to fail if the "PR Test" did not upload any artifact, especially ... 1. if the "PR Test"...

**To fix case 1**, we could run the "PR review companion" workflow conditionally only if the "PR Test" workflow run concluded with "success": > `if: ${{ github.event.workflow_run.conclusion == 'success' }}`...

Decreased priority, because it's just annoying, not _really_ a problem that the workflow fails.

Currently, the border properties are roughly ordered by appearance in the tool, except for `border-image-source`. It's true that a different order could make more sense.