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
ESML installs with Bower, but we rely on a separate repo for this support.
Getting the releases to line up correctly is proving tricky and involves a bit of work.
I'd like to be able to offer this easy install, but in a way that is maintainable.
What are the thoughts on using TravisCI to automatically create a release archive containing just traceur.js and traceur-runtime.js that would be uploaded as the GitHub release archive associated with the version tag.
ESML installs with Bower, but we rely on a separate repo for this support.
Getting the releases to line up correctly is proving tricky and involves a bit of work.
I'd like to be able to offer this easy install, but in a way that is maintainable.
What are the thoughts on using TravisCI to automatically create a release archive containing just traceur.js and traceur-runtime.js that would be uploaded as the GitHub release archive associated with the version tag.
This process can be automated by following I believe - http://docs.travis-ci.com/user/deployment/releases/.
Since I've never actually done it, I'd be happy to see if I can demonstrate this workflow on a test repo first before sending a PR if it helps.
Thoughts?
The text was updated successfully, but these errors were encountered: