You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if we'll actually want to run CI builds of the front-end unless we end up writing unit tests for front-end components, and I don't know all that much about unit testing for JS. However, Codacy has static analysis for JS and CSS, so we might want to look into that.
The text was updated successfully, but these errors were encountered:
If we do end up using this repo for front-end dev, we'd probably want to hook it into Slack as well. Might want to have separate #frontend and #backend channels so we don't get swamped with status messages from both repos, especially if we end up onboarding additional devs (I've mentioned it to at least one other person).
hawkw
changed the title
Set up CI and static analysis
Set up dev services
Jul 13, 2015
I don't know if we'll actually want to run CI builds of the front-end unless we end up writing unit tests for front-end components, and I don't know all that much about unit testing for JS. However, Codacy has static analysis for JS and CSS, so we might want to look into that.
The text was updated successfully, but these errors were encountered: