The repo already has Kind/*, Priority/*, Reviewed/*, and Status/* labels, but nothing to group issues by platform or area of the codebase (e.g. Etsy, Shopify, Amazon, Auth0/authentication, mock-platform layer). As more platform-integration milestones fill up with issues (see the Etsy Integration milestone), add a set of labels (e.g. Platform/Etsy, Platform/Shopify, Platform/Amazon, ...) and apply them to existing issues so tasks can be filtered/organized by area, not just by milestone.
The repo already has `Kind/*`, `Priority/*`, `Reviewed/*`, and `Status/*` labels, but nothing to group issues by platform or area of the codebase (e.g. Etsy, Shopify, Amazon, Auth0/authentication, mock-platform layer). As more platform-integration milestones fill up with issues (see the Etsy Integration milestone), add a set of labels (e.g. `Platform/Etsy`, `Platform/Shopify`, `Platform/Amazon`, ...) and apply them to existing issues so tasks can be filtered/organized by area, not just by milestone.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The repo already has
Kind/*,Priority/*,Reviewed/*, andStatus/*labels, but nothing to group issues by platform or area of the codebase (e.g. Etsy, Shopify, Amazon, Auth0/authentication, mock-platform layer). As more platform-integration milestones fill up with issues (see the Etsy Integration milestone), add a set of labels (e.g.Platform/Etsy,Platform/Shopify,Platform/Amazon, ...) and apply them to existing issues so tasks can be filtered/organized by area, not just by milestone.