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

Make HTML5 compatible and some little changes #65

Closed
wants to merge 5 commits into from
Closed

Make HTML5 compatible and some little changes #65

wants to merge 5 commits into from

Conversation

smartclash
Copy link

Okay, let's make it production ready. Can't we?

README.md Outdated
<head>
<link rel="stylesheet" href="https://cdn.rawgit.com/yegor256/tacit/gh-pages/tacit-VERSION.min.css"/>
<meta charset="UTF-8">
<link rel="stylesheet" href="https://cdn.rawgit.com/yegor256/tacit/gh-pages/tacit-0.8.1.min.css"/>
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This 0.8.1 will stay here even after we release, say, 0.9.0. We will have to remember that these numbers have to be modified manually every time we release a new version? :) Not really what continuous delivery is about.

</html>
```

Or simply download [`tacit.min.css`](https://raw.githubusercontent.com/yegor256/tacit/gh-pages/tacit.min.css)
Or simply download [`tacit.min.css`](https://cdn.rawgit.com/yegor256/tacit/gh-pages/tacit-0.8.1.min.css)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@smartclash the same problem here. We should not use explicit numbers in README.md

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@smartclash please, remove this change. We should point to the latest version always, in the README.

@yegor256
Copy link
Owner

@smartclash see some comments above

@smartclash
Copy link
Author

@yegor256 Sure, you are right. But the problem is, you are making this CSS file just for people who are complete noobs about web technologies and other things. And making them to go to the release section and fetch the version manually and including it is like a nightmare for them (provided they are complete noob).

So, that's why I am saying this. I hope you can understand. And hey, your rultor is awesome. I am using it for my project too.

@yegor256
Copy link
Owner

yegor256 commented May 1, 2017

@smartclash hey, it's just a single click to check the latest version in the "releases" section. Even a monkey can figure it out :) Let's remove that change from the PR and I'll merge it.

@smartclash
Copy link
Author

@yegor256 Okay, awesome. Let's make it up :)

@smartclash
Copy link
Author

DONE!!

@yegor256
Copy link
Owner

yegor256 commented May 1, 2017

@smartclash thanks! One more comment you seemed to forget.

@filfreire
Copy link
Collaborator

@smartclash can you solve the conflicts in README.md?
Thanks 👍

@filfreire
Copy link
Collaborator

@yegor256 the user @smartclash hasn't solved the conflicts since May and after I mentioned him 17 days ago. I believe we can close this PR.

@smartclash if you wish to re-open the PR I suggest fixing the conflicts and opening a new one, or doing the changes from a fresh start. Thank your for all your contributions 👍

@yegor256 yegor256 closed this Nov 1, 2017
@yegor256
Copy link
Owner

yegor256 commented Nov 1, 2017

@filfreire closed

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 this pull request may close these issues.

None yet

3 participants