Is your feature request related to a problem? Please describe.

Turret ammo spawns are an unfortunate balance issue: turrets are too easy a loot pinata for many players.

Solution you would like.

Ideally we should continue to reduce the use of turrets overall until eventually most of them are phased out except in particular special cases. However, a more short-term solution and one that w

I hope that all component reference docs indicates the name of component for referencing at the header, just like Vant:

Thanks a lot.

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

I j

Now that we have the checklocks analyzer, we should annotate values that are lock-protected with an appropriate checklocks attribute.

I looked into whether we can do this via react-native-bot but it seems like the candidates for the bot is based on Github search: https://github.com/hramos/react-native-bot/blob/master/lib/bot/pullrequests.rb#L48

So I think this might need to be a Github action.

Release branches should follow the form:
{major}.{minor}-stable

To monitor the asynq queue, it would be nice to periodically retrieve stats (like the asynq stats command currently does), but in a format which can be piped into monitoring tools.

A simple and easy way to do this would be to add a --json flag to asynq stats which outputs all gathered stats as json. This stats can then periodically be retrieved (with tools like Telegraf) and then display