| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
This updates a lot of comments.
|
@BridgeAR build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/2677/pipeline |
Sorry, something went wrong.
There was a problem hiding this comment.
RSLGTM, but are you willing to backport to the four current release branches (11, 10, 8, 6) so as to avoid endless merge conflicts going forward?
(I guess if churn is a concern, we can always try 45 or 49 instead of 40?)
Sorry, something went wrong.
|
@Trott yes, I am willing to do that. So far it seemed like the introduction of the rule itself did not cause any pain in backporting. It's probably because it's mostly just a single line in a comment and this can mostly be resolved automatically. |
Sorry, something went wrong.
There was a problem hiding this comment.
With in-passing nits, feel free to ignore or to address in a fixup commit/other PR.
Sorry, something went wrong.
Co-Authored-By: BridgeAR <ruben@bridgewater.de>
Co-Authored-By: BridgeAR <ruben@bridgewater.de>
There was a problem hiding this comment.
Thanks @BridgeAR 👍 👍
Sorry, something went wrong.
Sorry, something went wrong.
This updates a lot of comments. PR-URL: nodejs#26223 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
|
This needs a manual backport for v11.x, which should probably happen soon, given that this changed 200 files. It might also make sense to not land the bits that change the linter rules for the release branches, because that can get in the way of backporting this? (Maybe it could have been a separate commit? I know other people do it that way when modifying/adding/enabling linter rules.) |
Sorry, something went wrong.
This updates a lot of comments. PR-URL: #26223 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
|
I backported this directly to the staging branch. @addaleax I'll separate the PRs in the future. That is indeed a good way of dealing with that. In this case I just ran make lint-js-fix after resolving the conflict (one line had to be fixed) and adding that to other cases (two other lines had to be changed). |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This updates a lot of comments.
Checklist