* Re-enable the Actions workflow linter using the latest version
* Update to the latest actions-linter
* Update to the latest actions-linter
* Rely on secrets.FREEZE directly rather than setting a duplicate env var
* Fix workflow error by using secrets.FREEZE directly as this one doesn't actually set a duplicate env var in the first place!
* Update to latest actions-linter
* Use ${{}} expression syntax
* Readd env.FREEZE to necessary workflows since secrets cannot be checked in 'if' conditions
* Readd the comment to the GraphQL updating workflow about the FREEZE secret
* Upgrade actions-linter
* Update Dockerfile so it at least builds
* And get it running again!
* Update Dockerfile
* Create build-docker-image.yml
* Update build-docker-image.yml
* Update Dockerfile
* Update Dockerfile
* Delete build-docker-image.yml
### Why:
A lot of content gets mistranslated, some common patterns are: frontmatter date and enums getting translated, liquid tags get translated or go missing during the translation process. These translation errors are tough to catch, especially when they often come in huge PRs.
### What's being changed:
- Frontmatter is also getting linted against schema as part of `lint-files`
- When an environment variable `TEST_TRANSLATION` is passed,
- `lint-files` will run its tests against all files that have been newly translated (by git-diffing between `translations` branch and `main` branch), and
- results are outputted using a custom jest reporter. The output is formatted in a way that makes it easy to exclude the problematic translated files from being merged, and to share the errors with [localization support](https://github.com/github/localization-support/issues/489).
- Run the implemented translation test as part of the existing `Node.js Tests - Translations` workflow
Create a workflow that closes issues with short titles
Co-authored-by: chiedo <chiedo@users.noreply.github.com>
Co-authored-by: Lee Dohm <1038121+lee-dohm@users.noreply.github.com>
Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
Co-authored-by: Janice <janiceilene@github.com>
Use self hosted runners for docs-internal
Co-authored-by: chiedo <chiedo@users.noreply.github.com>
Co-authored-by: James M. Greene <JamesMGreene@github.com>