We still want Actions workflows to be able to change these files, so let's make the Actions environment exempt from this check by adding something like this toward the top of the file:

if (process.env.CI) process.exit()

In the Github Actions documentation (https://help.github.com/en/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables) it refers to some predefined environment variables and there is the one you comment, process.env.CI, so just adding the line you propose would be enough.

@zeke Done -> https://github.com/nodejs/nodejs.org/pull/3172/files#diff-6d229f474368307be4db86c19d5c3f7cR20

Since husky has been regarded as a footgun for developers by some of our contributors – and seeing that it has been added and removed from this repo multiple times due to that friction: elevating the conversation about how we want to handle commit-linting across the project (as @MylesBorins mentioned here) seems like the right thing to do – rather than reintroducing it here just to help the i18n initiative protect one repo that consumes its exports from commits made directly to it (which unintentionally green-lights its use for other cases in /nodejs.org). Imo, I agree that when there is project-wide consensus on how we want to enforce commit linting (eg. via husky or as a CI job), then we can be more confident on how we want 'source of truth' repos like /i18n to handle this in order to prevent direct commits elsewhere. 👍

Given that, I'm going to request that we at the very least:

• Hear more opinions here about approving this PR which reintroduces husky into this repo, and hopefully get greater consensus on that beyond the folks who're involved with i18n and nodejs.org.
• Elevate the conversation accordingly to the TSC via admin.

cc @alexandrtovmach @zeke @MylesBorins

cc @nodejs/website

I haven't read all the historical context as it pertains to use of husky in the @nodejs org, but if we are going to remove husky, is there some alternative mechanism now being used by the @nodejs project to lint commits?

@zeke, I think for linting js files, standard is being used. As shown in this snippets,

If its requires to npm run test before each commit, then standard should lint the js file while other modules are used in parallel to lint different type of files as shown above.