.travis.yml & build.sh: add html5validator & profiling #900

Closed
Mikaela wants to merge 2 commits from travis into master
Mikaela commented 2019-05-04 11:56:42 +00:00 (Migrated from github.com)

Enable html5validator and jekyll profiling.

We aren't valid HTML5 currently. I blacklisted classic, because I think it's taking errors that aren't errors on the new site and I am in belief that it's not cared about that much.

Enable html5validator and jekyll profiling. We aren't valid HTML5 currently. I blacklisted classic, because I think it's taking errors that aren't errors on the new site and I am in belief that it's not cared about that much.
netlify[bot] commented 2019-05-04 11:57:21 +00:00 (Migrated from github.com)

Deploy preview for privacytools-io ready!

Built with commit 72a6a4a979

https://deploy-preview-900--privacytools-io.netlify.com

Deploy preview for *privacytools-io* ready! Built with commit 72a6a4a979aef8f11754c5684d6bf9da511638d1 https://deploy-preview-900--privacytools-io.netlify.com

I'm not sure how travis works.

I'm not sure how travis works.
Mikaela commented 2019-05-15 08:13:29 +00:00 (Migrated from github.com)

@Shifterovich ping? :)

@Shifterovich ping? :)
nitrohorse (Migrated from github.com) requested changes 2019-07-21 00:17:47 +00:00
nitrohorse (Migrated from github.com) left a comment

Based on the Travis build log, it looks like your commit for adding html5validator is actually working fine which is great and thus fails because of these existing validation errors.

I think before approving, we should update this PR to include fixes for these errors. That way we set a new baseline of validated HTML, the build will pass, and then subsequent PRs will get validation error checking based solely on the author's changes.

Based on the [Travis build log](https://travis-ci.com/privacytoolsIO/privacytools.io/builds/110611519), it looks like your commit for adding html5validator is actually working fine which is great and thus fails because of [these existing validation errors](https://bin.disroot.org/?497f72958cd96134#Ybm13xgJJPwGLhVDEkt4z3ux5zYTBkLQlDXRqparuSg=). I think before approving, we should update this PR to include fixes for these errors. That way we set a new baseline of validated HTML, the build will pass, and then subsequent PRs will get validation error checking based solely on the author's changes.
nitrohorse commented 2019-08-17 04:16:02 +00:00 (Migrated from github.com)

I think we can close and fold this into https://github.com/privacytoolsIO/privacytools.io/issues/1093.

I think we can close and fold this into https://github.com/privacytoolsIO/privacytools.io/issues/1093.
This repo is archived. You cannot comment on pull requests.
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#900
No description provided.