GitHub is very much lacking a tool to find PRs that touch the same files as yours. This becomes very problematic when you have over a thousand of them, like we do in #GodotEngine.

While we're waiting for GitHub to recognize this issue, I've made a custom tool for Godot maintainers and contributors :)

https://yurisizov.github.io/godot-prs-by-file/

For a moment it's on my account, but we should move it under the org soon enough.

Godot PRs by File

Godot Engine PRs grouped by individual source files they affect

@yurisizov you seen this, @dcreager ? seems tractable.
@sixwing @yurisizov I haven’t! But I live near the relevant team now and I can pass this on to them

@dcreager @sixwing If you do end up passing this on, tell their product manager that I'm sorry for not using any proper channels to reach out!

To be honest, I'm not entirely sure what would be a good channel that won't be drowned by other tickets (I guess you have your own issue with the influx :D). Something like the new maintainers lounge that we have but for technical stuff could be nice.

Still, no blame, the API is there for me to achieve all that myself :)

@yurisizov I think the merge queues experimental feature is supposed to help, but it doesn't address the whole issue

@teivel Unfortunately, no, this is a different area. This tool is for the review and approval stage to look for possible conflicts, and also for contributors to check if someone might've worked in the same area they are planning to target.

We looked at merge queues for a different reason, though. We need a tool to bulk-merge PRs to avoid CI congestion on the main branch. Sadly, MQs do the opposite, and create more congestion as we have very expensive builds.