Just checking: are you aware of tryserver.get_files_affected_by_patch ?

Yeah. That function performs a "git diff", which is redundant with bot_update simply declaring which files are affected as part of its operation. The latter is preferable because:
- bot_update already knows this information, since it's the entity that's doing the patching.
- the affected files would show up in the bot_update JSON response, which is useful for understanding things.

If "bot_update" wants to use "git diff" to figure out what changed, that's fine, but I think it's bot_update's responsibility.

This has been listed as untriaged for over two weeks. Marking available.

Since the priority is P-1, dropping it.

If you disagree with either of these actions (bulk edit), please fix.

+Edward: since you've moved this feature to gclient, is it feasible to somehow expose this back to bot_update?

+agable.
I'll take a look once I finished moving it to gclient.