We've had a few rounds of the automatic instructions updates - I've seen some decent ones come through, but they're starting to pile up (https://github.com/Azure/azure-dev/issues?q=is%3Aissue+state%3Aopen+%5Bauto%5D+instructions+author%3Aapp%2Fgithub-actions). This issue is a nice background task to go take a look at the pile-up, see if we have a better way to handle it (perhaps it should run over a longer interval, so the update is more meaty) and also see how we've been doing.
In particular, I've been working on a rather difficult change for layered provisioning, and I feel like the skill hasn't been attributed for any of the comments, which makes me think we're missing something - perhaps we need another "lens" for one of our reviewers, or , but it'd be great to catch more.
This is probably an ongoing task, but I'd like to start picking away at it.
We've had a few rounds of the automatic instructions updates - I've seen some decent ones come through, but they're starting to pile up (https://github.com/Azure/azure-dev/issues?q=is%3Aissue+state%3Aopen+%5Bauto%5D+instructions+author%3Aapp%2Fgithub-actions). This issue is a nice background task to go take a look at the pile-up, see if we have a better way to handle it (perhaps it should run over a longer interval, so the update is more meaty) and also see how we've been doing.
In particular, I've been working on a rather difficult change for layered provisioning, and I feel like the skill hasn't been attributed for any of the comments, which makes me think we're missing something - perhaps we need another "lens" for one of our reviewers, or , but it'd be great to catch more.
This is probably an ongoing task, but I'd like to start picking away at it.