-
Notifications
You must be signed in to change notification settings - Fork 10
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
Setup ESLint in order to lint JavaScript #568
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(maybe also something for another PR?)
Splines
added
the
CI/CD
Continuous Integration / Continuous Delivery (aka pipeline stuff)
label
Dec 6, 2023
Splines
changed the title
Add ESLint to Lint JavaScript in .js and .js.erb files & add sensible VSCode defaults
Add ESLint to Lint JavaScript & add sensible VSCode defaults
Dec 6, 2023
Splines
force-pushed
the
lint/js
branch
6 times, most recently
from
December 6, 2023 17:21
b41e342
to
425a27e
Compare
Splines
changed the title
Add ESLint to Lint JavaScript & add sensible VSCode defaults
Add ESLint to Lint JavaScript
Dec 6, 2023
Splines
changed the title
Add ESLint to Lint JavaScript
Add ESLint in order to lint JavaScript
Dec 6, 2023
Splines
changed the title
Add ESLint in order to lint JavaScript
Add ESLint to pipeline in order to lint JavaScript
Dec 6, 2023
Splines
changed the title
Add ESLint to pipeline in order to lint JavaScript
Setup ESLint in order to lint JavaScript
Dec 6, 2023
fosterfarrell9
approved these changes
Dec 13, 2023
This was referenced Dec 19, 2023
Splines
added a commit
that referenced
this pull request
Jan 6, 2024
* Init new ESLint config to lint .js and .js.erb files * Add default settings/extensions for VSCode (maybe also something for another PR?) * Add ESLint to CI/CD * Introduce dummy changes to see ESLint in action * Fix wrong fetch depth for checkout action * Remove unnecessary "--" to pass arguments * Outsource retrieval of changed files to reusable action * Correct location of reusable action * Fix further stuff related to GitHub action * Clean up GitHub Actions files * Cache global yarn cache directory * Remove VSCode specific settings in favor of #569 * Revert "Introduce dummy changes to see ESLint in action" This reverts commit cdf3473.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds ESLint to our CI/CD pipeline and checks for linting violations in all changed
.js
and.js.erb
files.Adding a sensible VSCode
settings.json
was outsourced to #569Sample output
See
this runthis run. The following screenshot was recorded in theFiles changed
tab on GitHub.