-
Notifications
You must be signed in to change notification settings - Fork 30
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
updated with "Learn" infobar. #6
Conversation
Oh, also moved component.json -> bower.json and did a version bump to 0.1.7. Happy to pull those out if you prefer. |
@@ -1,4 +1,4 @@ | |||
{ | |||
"name": "todomvc-common", | |||
"version": "0.1.6" | |||
"version": "0.1.7" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ya, don't bump as it's easier to just do npm version
which bumps number and tags
@sindresorhus Just updated. Is that what you were thinking? Here's the new template:
If there's a better way to do the template or the code, let me know. When we finalize this, I'll send in a PR to TodoMVC with the new code / updated learn.json file. |
I like it. Definitely easier to read. :) |
Agreed! |
👍 |
Updated to please tastejs/todomvc#568. |
Go for it! :) |
updated with "Learn" infobar.
I'm not sure how to do the version bump without manually editing bower.json. What's the ideal procedure to do a release? |
That's actually what I did so far for bower components. Manually edit, tag and push. |
(TodoMVC:#547)
The new files!