-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to use new actions-utils that is aware of ALL_CHANGED_FILES #28
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thank you!
format: 'json' # robust to filenames with spaces | ||
absolute: true # our tooling expects absolute paths | ||
|
||
# Now we put it on the environment so that it can be |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...can be??
@@ -10,24 +10,24 @@ jobs: | |||
runs-on: ubuntu-latest | |||
steps: | |||
- name: Run eslint | |||
uses: Khan/eslint-action@main | |||
setup: yarn | |||
uses: Khan/eslint-action@da16c43dd352e1e606c838008e7f25e3bf3fbf97 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would we revert this to main
once this lands? or...?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah I can change it before landing
Summary:
See Khan/actions-utils#14
Test plan:
I updated the workflow to set up the ALL_CHANGED_FILES variable. Our other workflows that use eslint-action will want to add those setup steps as well.