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

Enforce new code must have no errors or warns #27

Merged
merged 1 commit into from
Jan 17, 2017

Conversation

jpwhite4
Copy link
Member

Description

Travis Ci will run the linter on any modifed js or php files. If
there are errors or warnings, then lint will be run on the previous
version of the file. If new errors or warning have been introduced then
the build is in error.

Motivation and Context

Improve the code quality for new code without putting an undue burden on developers to fix the existing code.

Tests performed

Tested using travis during development. Already running with this code on the xdmod-supremm module and tested by creating pull requests with different code changes.

@plessbd plessbd changed the title Enforce new code must have not errors or warns Enforce new code must have no errors or warns Jan 14, 2017
Travis Ci will run the linter on any modifed js or php files. If
there are errors or warnings, then lint will be run on the previous
version of the file (if there was one). If new errors or warning have been introduced then
the build is in error.
@jpwhite4 jpwhite4 merged commit 8118806 into ubccr:xdmod6.6 Jan 17, 2017
@jpwhite4 jpwhite4 deleted the lint branch January 17, 2017 16:00
@tyearke tyearke added the qa label Jan 18, 2017
@tyearke tyearke added this to the v6.6.0 milestone Jan 18, 2017
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