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

Linting in CI #137

Closed
1 of 2 tasks
rwjblue opened this issue Apr 18, 2016 · 1 comment · Fixed by #214
Closed
1 of 2 tasks

Linting in CI #137

rwjblue opened this issue Apr 18, 2016 · 1 comment · Fixed by #214

Comments

@rwjblue
Copy link
Member

rwjblue commented Apr 18, 2016

We need to ensure that new PR's do not introduce type issues, I see the path for this something like the following:

  • Add npm run vscode-build to .travis.yml's script (this will get at least a pass/fail for PR's until better testing can get setup).
  • Incorporate broccoli-tslinter to enable live reload style testing.
rwjblue added a commit that referenced this issue Apr 18, 2016
Addresses one point from #137.
chancancode pushed a commit that referenced this issue Apr 18, 2016
Addresses one point from #137.
krisselden pushed a commit that referenced this issue Apr 20, 2016
Addresses one point from #137.
@GavinJoyce GavinJoyce mentioned this issue Jul 13, 2016
4 tasks
@GavinJoyce
Copy link
Contributor

GavinJoyce commented Jul 24, 2016

This can be closed now (I forgot to add closes #xyz to the PR)

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 a pull request may close this issue.

3 participants