coala / projects

A website that showcases interesting projects, using Angular JS.
https://projects.coala.io/
GNU Affero General Public License v3.0
116 stars 223 forks source link

Use CSSLintBear #761

Closed KVGarg closed 4 years ago

KVGarg commented 5 years ago

The commit adds a new section in .coafile which will be responsible for linting css files and, check if there are any error or not.

abhishalya commented 4 years ago

@KVGarg Can you rebase this PR, it would good to merge this one first.

TravisBuddy commented 4 years ago

Hey @KVGarg, Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: b8710a60-8d1f-11ea-bfcd-ab7027f5d872
abhishalya commented 4 years ago

@KVGarg The CI should pass now, seems like there's some other issue.

KVGarg commented 4 years ago

@KVGarg The CI should pass now, seems like there's some other issue.

Yeah! the ruby bundler isn't found

TravisBuddy commented 4 years ago

Hey @KVGarg, Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: fa45ff70-8d21-11ea-bfcd-ab7027f5d872
TravisBuddy commented 4 years ago

Hey @KVGarg, Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: 49d1eb80-8d22-11ea-bfcd-ab7027f5d872
TravisBuddy commented 4 years ago

Hey @KVGarg, Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: 5baa66c0-8d22-11ea-bfcd-ab7027f5d872
TravisBuddy commented 4 years ago

Travis tests have failed

Hey @KVGarg, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: 6fe7dea0-8d23-11ea-bfcd-ab7027f5d872
TravisBuddy commented 4 years ago

Travis tests have failed

Hey @KVGarg, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: 32e6e300-8d25-11ea-bfcd-ab7027f5d872
KVGarg commented 4 years ago

@abhishalya ready to be merged

TravisBuddy commented 4 years ago

Hey @KVGarg, Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: 27df2980-8d53-11ea-bfcd-ab7027f5d872
abhishalya commented 4 years ago

@KVGarg Hmm, not sure what is happening with travis since it should use bundler 1.x as in the Gemfile.lock (as it does for the existing master build). Okay, for now we had enough of this. Let's just manually install bundler and fix this. If we find a better solution, a PR would be fine imo.

abhishalya commented 4 years ago

@KVGarg Check https://github.com/abhishalya/projects/tree/upstream/%23761 the config there works.

KVGarg commented 4 years ago

Maybe the bundler was not getting installed in stage test that I declared :rofl: I don't know why I declared that new stage :thinking:

TravisBuddy commented 4 years ago

Travis tests have failed

Hey @KVGarg, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: 202b8000-8d60-11ea-bfcd-ab7027f5d872
KVGarg commented 4 years ago

Finally! A green check from travis