Howard Edwards

> ... I updated the URLs for landmark information in the index and coverage scripts. How do I run them in this pull request to see if they generate the...

> ... I've submitted [wai-aria-practices#382](https://github.com/w3c/wai-aria-practices/pull/382) to relax this constraint instead. @jongund https://github.com/w3c/wai-aria-practices/pull/382 has been merged now so the Landmarks page renders in the [generated preview](https://deploy-preview-383--aria-practices.netlify.app/aria/apg/patterns/landmarks/) now. Just the coverage report...

> but figuring out what's changed and pulling that bump into its own PR shouldn't be an issue based on how the grouped PR is presented Looking again at the...

> > Looking again at the grouped PR, change notes on `lint-staged`, `prettier` and `selenium-webdriver` were left off at the end. Unsure why. > > I wonder if the size...

> 1. Is the feature designed to retain assignees in the test queue In short, yes. If the results of each copied test, in a run which are directly tied...

Sure, I'll have a look into how that logic works. But perhaps @alflennik may have more context on what I believe is the GQL based, conflicts resolver that's being discussed.

Drafting for now as this work will need a matching `w3c/aria-at-app` PR to support these changes during test plan version imports

Closing since work included in #1334

https://github.com/w3c/aria-at/pull/1108#issuecomment-2296957598 > You're right, it looks like there isn't anything native to git that will clean out the BOM. The `encoding` is set in `.editorconfig`, but I'm not sure how...

> Option 1: Move to about section > > * Pro: more visible I'm not sure this is a valuable advantage because code contributors need to read the readme anyway....