meta: investigate "incorporating feedback in your pull request"

[vsemozhetbyt]

New GitHub feature:

https://help.github.com/articles/incorporating-feedback-in-your-pull-request/#applying-a-suggested-change

This can simplify nits addressing. We may need to update our contributing guides (including how-to steps to sync local branches with remote changes if needed).

[vsemozhetbyt]

Example: #23701 (comment)

[refack]

Example2: https://github.com/nodejs/node/pull/22079/files#r225699740

IMHO it's a very nice feature for reviewers who are willing to make the extra effort.
We do need to be a little bit careful since GitHub is not an IDE, so when suggesting code changes it should be stated explicitly if it was tested, or is pseudocode.

[refack]

We may need to update our contributing guides (including how-to steps to sync local branches with remote changes if needed).

I believe there's a balance to strike here. IMHO our contribution guide should focus on the things that are specific to work in this repo. While points that require general git and GitHub literacy should be referred to better guides. Such as the new https://lab.github.com/

[vsemozhetbyt]

A doubt: technically, any Collaborator can assign themselves to a PR and accept an own proposed change. This can alleviate nit addressing for the PR author, but also can be felt like a bit arbitrarily thing.

[vsemozhetbyt]

It seems this is not possible.