cotes2020 / jekyll-theme-chirpy

A minimal, responsive, and feature-rich Jekyll theme for technical writing.
https://chirpy.cotes.page
MIT License
7.58k stars 5.93k forks source link

HTML-Proofer Finding Failures After Uploading CSS File #317

Closed grantwforsythe closed 3 years ago

grantwforsythe commented 3 years ago

Checklist

Description

Hello,

I wanted to justify the text like in #172 but I have since broken my website. My build failed when I tried uploading css\style.scss. Why would this have caused an issue? The error is as follows,

- _site/404.html
  *  https:// is an invalid URL (line 1)
     <link rel="preconnect" href="https://" crossorigin="use-credentials">
  *  https:// is an invalid URL (line 1)
     <link rel="dns-prefetch" href="https://">
- _site/about/index.html
  *  https:// is an invalid URL (line 1)
     <link rel="preconnect" href="https://" crossorigin="use-credentials">
  *  https:// is an invalid URL (line 1)
     <link rel="dns-prefetch" href="https://">
- _site/archives/index.html
  *  https:// is an invalid URL (line 1)
     <link rel="preconnect" href="https://" crossorigin="use-credentials">
  *  https:// is an invalid URL (line 1)
     <link rel="dns-prefetch" href="https://">
- _site/categories/blogging/index.html
  *  https:// is an invalid URL (line 1)
     <link rel="preconnect" href="https://" crossorigin="use-credentials">
  *  https:// is an invalid URL (line 1)
     <link rel="dns-prefetch" href="https://">
- _site/categories/index.html
  *  https:// is an invalid URL (line 1)
     <link rel="preconnect" href="https://" crossorigin="use-credentials">
  *  https:// is an invalid URL (line 1)
     <link rel="dns-prefetch" href="https://">
- _site/categories/philosophy/index.html
  *  https:// is an invalid URL (line 1)
     <link rel="preconnect" href="https://" crossorigin="use-credentials">
  *  https:// is an invalid URL (line 1)
     <link rel="dns-prefetch" href="https://">
- _site/index.html
  *  https:// is an invalid URL (line 1)
     <link rel="preconnect" href="https://" crossorigin="use-credentials">
  *  https:// is an invalid URL (line 1)
     <link rel="dns-prefetch" href="https://">
- _site/posts/freedom-of-speech/index.html
  *  https:// is an invalid URL (line 1)
     <link rel="preconnect" href="https://" crossorigin="use-credentials">
  *  https:// is an invalid URL (line 1)
     <link rel="dns-prefetch" href="https://">
- _site/princples/index.html
  *  https:// is an invalid URL (line 1)
     <link rel="preconnect" href="https://" crossorigin="use-credentials">
  *  https:// is an invalid URL (line 1)
     <link rel="dns-prefetch" href="https://">
- _site/tags/index.html
  *  https:// is an invalid URL (line 1)
     <link rel="preconnect" href="https://" crossorigin="use-credentials">
  *  https:// is an invalid URL (line 1)
     <link rel="dns-prefetch" href="https://">

HTML-Proofer found 20 failures!
Ran on 13 files!

I have tried to rolling back to previous commits thinking that would resolve the issue but that was not the case.

cotes2020 commented 3 years ago

This is because I released version 3.4.0 yesterday, which made incompatible configuration changes. You can lock the Gemfile version to 3.3.x, or update your repository files to follow the starter template.

In order to strictly adhere to the specification for semantic versioning, I will change the version 3.4.0 to 4.0.0 later.

grantwforsythe commented 3 years ago

Thanks, @cotes2020, that has resolved my issue.

Going forward, is there a straightforward way to keep the generated repo update? I suppose just adding a remote?

cotes2020 commented 3 years ago

Yes, you can add an upstream branch to track file changes in the starter template.

grantwforsythe commented 3 years ago

Cheers, thanks for your assistance.