Skip to content
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 13 commits into from
Dec 19, 2023
Merged

Setup ESLint in order to lint JavaScript #568

merged 13 commits into from
Dec 19, 2023

Conversation

Splines
Copy link
Member

@Splines Splines commented Dec 6, 2023

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 #569

Sample output

See this run this run. The following screenshot was recorded in the Files changed tab on GitHub.

@Splines Splines self-assigned this Dec 6, 2023
@Splines Splines changed the base branch from main to mampf-next December 6, 2023 00:12
@Splines Splines added the CI/CD Continuous Integration / Continuous Delivery (aka pipeline stuff) label Dec 6, 2023
@Splines 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 Splines force-pushed the lint/js branch 6 times, most recently from b41e342 to 425a27e Compare December 6, 2023 17:21
@Splines Splines changed the title Add ESLint to Lint JavaScript & add sensible VSCode defaults Add ESLint to Lint JavaScript Dec 6, 2023
@Splines Splines marked this pull request as ready for review December 6, 2023 17:48
@Splines Splines changed the title Add ESLint to Lint JavaScript Add ESLint in order to lint JavaScript Dec 6, 2023
@Splines Splines changed the title Add ESLint in order to lint JavaScript Add ESLint to pipeline in order to lint JavaScript Dec 6, 2023
@Splines Splines changed the title Add ESLint to pipeline in order to lint JavaScript Setup ESLint in order to lint JavaScript Dec 6, 2023
@Splines Splines merged commit b421193 into mampf-next Dec 19, 2023
5 checks passed
@Splines Splines deleted the lint/js branch December 19, 2023 09:54
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
Labels
CI/CD Continuous Integration / Continuous Delivery (aka pipeline stuff)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants