René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Improve finding issues without a pull request to work on","articleBody":"As a newbie to the CPython repository, it can be quite frustrating to find issues that have not an associated pull request.\n\nThe `linked:pr` has a small coverage and requires manual intervention (ie. a \"closes\" or \"fixes\" magic keyword in the description). Moreover, the linked:pr will close the associated issue on merge, and sometimes the issue should be kept open (because of retrocompatibility PRs, and others that I can not yet grasp).\n\nThe GitHub API exposes another concept (cross references) and these appear in the history of an issue. This is why I first implemented a script to list all the issues and the associated PRs. The output looks [like this](https://docs.google.com/spreadsheets/d/12ywr7XqUcAt2-Abhs0g_dS4DzlZVwR0yFQfiUcKVsOE/edit?gid=2062761302#gid=2062761302). But this is not a scalable solution: the GitHub API could suffer if all the newbies were to use it, and the script needs to be executed often to keep the picture up to date with reality.\n\nGiven that the cross-references are essentially events, why don't we add a github workflow that\n- adds a `has-pr` label when a PR is created, referencing an issue in its title or in its description\n- adds a `has-pr` label when a comment is added to the PR mentioning an issue\n- removes the `has-pr` label when the PR is closed without being merged\n\nI have a sample GitHub Actions workflow available on the [nilleb/cpython-stub](https://github.com/nilleb/cpython-stub) repository\n\nA [discussion has been opened on Discourse](https://discuss.python.org/t/finding-issues-without-a-pull-request-to-work-on/103554/10).","author":{"url":"https://github.com/nilleb","@type":"Person","name":"nilleb"},"datePublished":"2025-09-05T09:46:14.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":16},"url":"https://github.com/581/core-workflow/issues/581"}