From: Patrick Talbert on gitlab.com
This is due to a flaw in the logic of the updated ack_nack bot:
The idea was that if an MR touched a redhat/configs/CONFIG file then we'd find
the corresponding Kconfig file and look up the Kconfig path in owners.yaml to
find relevant reviewers. But of course with something like NODES_SHIFT that
matches many different arch Kconfig files 🤦.
So I need to improve the logic to determine if the CONFIG file is in an arch-
specific location and then filter any found Kconfigs based on that. But until
that happens (next week?) you may find yourself added as a reviewer for the
odd MR that is not relevant to you. Please ignore it.