GitHub Issues Migration is coming soon

[ezio-melotti]

@CAM-Gerlach

@-mentions requires actually making a comment on the PR with the mentions, which pings everyone subscribed in addition to the person mentioned, increases clutter, and is somewhat more effort

It might be possible to edit the first message to add mentions, similarly to what bedevere does when adding a link to the bpo issue, however I’m not 100% sure that works. I think edited lines and re-evaluated and should trigger @mention notifications, but they won’t send emails to other subscribers. This is a bit tricky to test since it requires multiple accounts and it’s also affected by the “watch” settings and other things. There is also no way to see the list of subscribers afaik.

To summarize the last few posts:

• the CODEOWNERS file:
  • only works for PRs (not issues)
  • automatically add people as reviewers
  • people have to add themselves to the file
• label-subscriptions:
  • work for both PRs and issues
  • subscribe the user automatically
  • people have to follow existing labels
• @mentions:
  • work for both PRs and issues
  • someone (bot or human) has to @mention
  • add some extra clutter

@brettcannon

The key thing to understand is those two lists are in separate repos. Probably the closest you could come is some GHA that tries to open a PR on the other repo when the key file has been opened.

In Add github usernames to the experts index · Issue #507 · python/devguide · GitHub it was proposed to store information in a JSON file that can be used to generate multiple files, possibly in separate repos.
We already have lists of devs in multiple places, including:

• The list of core devs and their info in a file in python/voters, updated manually
• The developers.csv file in python/devguide, generated from the voters list
• The Developer Log in the devguide, generated from the csv
• The Experts Index in the devguide, updated manually
• The nosy list autocomplete on bpo (not for long), generated from the experts index (also available through an API)
• The CODEOWNERS file, updated manually

Also note that the Experts Index has five sections:

• Stdlib: can be mapped to CODEOWNERS and some labels
• Tools: only has 2 tools, one has a label (argument-clinic)
• Platforms: has 7 (used) platforms, only two labels (OS-windows, OS-mac)
• Miscellaneous: ~40 entries, only ~6 labels
• Documentation Translations: 8 entries, no matching labels

IOW, the CODEOWNERS file could replace the stdlib section (and the section could be removed from the expert index), but not the other sections. For the other sections, the only ways to automate subscriptions are:

• Create even more labels people can subscribe to
• Create GitHub teams and @mention the team
• Have triagers directly @mention experts from the list

Note that in all cases we would have to rely on triagers to either add the right labels, or mentioning the teams/users. In addition, labels also allow external people to follow certain issues, whereas teams and direct mentions don’t. The downside is that the more labels there are, the more difficult the triaging becomes.