René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add type-behavior label for CPython PRs","articleBody":"\u003c!--\r\n\r\nFeature-request/bug specific to GitHub bots/tools can be reported in their own repositories:\r\n\r\nthe-knights-who-say-ni: https://github.com/python/the-knights-who-say-ni\r\nbedevere: https://github.com/python/bedevere\r\nblurb-it: https://github.com/python/blurb-it\r\nmiss-islington: https://github.com/python/miss-islington\r\n\r\nBroader core-workflow issues can be discussed here, or in Discourse: \r\n\r\nhttps://discuss.python.org/c/core-workflow\r\n\r\n--\u003e\r\n\r\nWith the existing labels for CPython PRs, I think a `type-behavior` label could be quite useful for describing PRs that involve changes in functionality and don't add new features (which would be covered by `type-enhancement`). This label already exists on BPO, and frequently feels missing on GitHub. It may not seem incredibly important at the moment, but I think it will be more noticeable as we transition to GitHub issues.\r\n\r\nAs a concrete example of a PR that it would be well suited towards, I recently opened a [PR](https://github.com/python/cpython/pull/19149) that makes an internal change in `concurrent.futures` to not use daemon threads for compatibility with subinterpreters. A `type-behavior` label would definitely be appropriate, while none of the others would quite fit.\r\n\r\nI can also think of quite a few other types of PRs that it could be well suited towards, such as new warnings (including deprecation, resource, etc), removals, and any other code changes in the internals that wouldn't qualify as a bug fix, performance optimization, or enhancement.\r\n\r\nThe addition of the label should be rather straightforward, as it would not include any new functionality or act as a trigger for a bot action.","author":{"url":"https://github.com/aeros","@type":"Person","name":"aeros"},"datePublished":"2020-03-25T07:15:18.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/364/core-workflow/issues/364"}