Skip to content

chore: add editorconfig-checker/action-editorconfig-checker#491

Merged
dfoulks1 merged 1 commit intoapache:mainfrom
erisu:chore/add-action-editorconfig-checker
Feb 27, 2026
Merged

chore: add editorconfig-checker/action-editorconfig-checker#491
dfoulks1 merged 1 commit intoapache:mainfrom
erisu:chore/add-action-editorconfig-checker

Conversation

@erisu
Copy link
Copy Markdown
Member

@erisu erisu commented Feb 19, 2026

Request for adding a new GitHub Action to the allow list

Overview

This GitHub Action, which wraps the editorconfig-checker tool, to check if the files follows the .editorconfig rules.

Name of action:

editorconfig-checker/action-editorconfig-checker

URL of action:

https://github.com/editorconfig-checker/action-editorconfig-checker

Version to pin to (hash only):

4b6cd6190d435e7e084fb35e36a096e98506f7b9 -> v2.1.0

Permissions

  • None that I can see.

In terms of workflow that would use this action, only the following permission block is defined:

    permissions:
      contents: read

Related Actions

None that I could find

Checklist

You should be able to check most of these boxes for an action to be considered for review.
Please check all boxes that currently apply:

  • The action is listed in the GitHub Actions Marketplace
  • The action is not already on the list of approved actions
  • The action has a sufficient number of contributors or has contributors within the ASF community
  • The action has a clearly defined license
    • MIT License
  • The action is actively developed or maintained
    • Last version released: 4 months ago
    • Last commit to main branch: within 1 week
  • The action has CI/unit tests configured
    • Has some sort of GHA workflow
      • Compare the expected and actual dist/ directories
      • Dependabot automerge
    • Does not appear to have unit testing.

@dfoulks1 dfoulks1 merged commit 24ece39 into apache:main Feb 27, 2026
6 checks passed
potiuk added a commit that referenced this pull request Mar 30, 2026
…dling

The Docker container was hardcoded to node:20-slim, causing large spurious
diffs when verifying actions built with a different Node.js version (e.g.
azure/setup-helm v5.0.0 which switched to node24). Now detects the Node.js
version from the action's action.yml `using:` field before building.

Also fix the PR diff extraction regex to match `use:` in addition to `uses:`
so that PRs with this common typo (e.g. #491) can still be processed.

Generated-by: Claude
potiuk added a commit that referenced this pull request Mar 30, 2026
…dling

The Docker container was hardcoded to node:20-slim, causing large spurious
diffs when verifying actions built with a different Node.js version (e.g.
azure/setup-helm v5.0.0 which switched to node24). Now detects the Node.js
version from the action's action.yml `using:` field before building.

Also fix the PR diff extraction regex to match `use:` in addition to `uses:`
so that PRs with this common typo (e.g. #491) can still be processed.

Generated-by: Claude
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants