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

chore: exec lint as separate CI step #1255

Merged
merged 1 commit into from
Nov 26, 2018
Merged

Conversation

jeeyyy
Copy link
Contributor

@jeeyyy jeeyyy commented Nov 22, 2018

Execute lint as a separate step in CI.

Closes issue: #1252

Reviewer checks

Required fields, to be filled out by PR reviewer(s)

  • Follows the commit message policy, appropriate for next version
  • Has documentation updated, a DU ticket, or requires no documentation change
  • Includes new tests, or was unnecessary
  • Code is reviewed for security by: @WilcoFiers

@jeeyyy jeeyyy requested a review from a team as a code owner November 22, 2018 13:35
@jeeyyy
Copy link
Contributor Author

jeeyyy commented Nov 22, 2018

@WilcoFiers - we need to enable lint check as a required step above.

@@ -61,6 +69,10 @@ workflows:
build:
jobs:
- dependencies
# Run linting
- lint:
requires:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this go into the job definition for lint above?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so. Requires is part of the workflow:
https://circleci.com/docs/2.0/configuration-reference/#requires

@WilcoFiers WilcoFiers merged commit 439b826 into develop Nov 26, 2018
@WilcoFiers WilcoFiers deleted the run-eslint-parallel branch November 26, 2018 16:32
stephenmathieson added a commit that referenced this pull request Jan 30, 2019
This patch removes all of the ESLint stuff from the Grunt configuration. There have been numerous efforts to "fix" the existing Grunt/ESLint setup which all seem unnecessary. Now, if you want to lint your code, just do `npm run eslint`. If you don't want to lint your code, then don't do `npm run eslint`.

Ref: #1342, #1314, #1267, #1255, #1247, and probably others...
WilcoFiers pushed a commit that referenced this pull request Feb 1, 2019
This patch removes all of the ESLint stuff from the Grunt configuration. There have been numerous efforts to "fix" the existing Grunt/ESLint setup which all seem unnecessary. Now, if you want to lint your code, just do `npm run eslint`. If you don't want to lint your code, then don't do `npm run eslint`.

Ref: #1342, #1314, #1267, #1255, #1247, and probably others...

## Reviewer checks

**Required fields, to be filled out by PR reviewer(s)**
- [x] Follows the commit message policy, appropriate for next version
- [x] Has documentation updated, a DU ticket, or requires no documentation change
- [x] Includes new tests, or was unnecessary
- [x] Code is reviewed for security by: @WilcoFiers
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.

3 participants