Copy link Copy Markdown

Member

Choose a reason for hiding this comment

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

should this be https?

Copy link Copy Markdown

Contributor Author

Choose a reason for hiding this comment

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

Probably 😝 but I just did the same PR to the other repos in the org like this. I'm going to check to see if they're going to set up the HTTPS redirect on the site

Copy link Copy Markdown

Member

Choose a reason for hiding this comment

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

:rip: time to fix them all 😆

Copy link Copy Markdown

Member

Choose a reason for hiding this comment

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

(just in the sass org):

$ all-repos-grep -C all-repos-sass.json http://sass-lang.com | wc -l
753
$ all-repos-grep -C all-repos-sass.json https://sass-lang.com | wc -l
9
$ all-repos-grep -C all-repos-sass.json http://sass-lang.com | cut -d':' -f1 | sort | uniq -c | sort -rn
    684 output-sass/sass/sass-spec
     23 output-sass/sass/ruby-sass
     15 output-sass/sass/sass
      5 output-sass/sass/sass-site
      5 output-sass/sass/node-sass
      5 output-sass/sass/libsass
      4 output-sass/sass/sass-registry
      4 output-sass/sass/dart-sass
      2 output-sass/sass/sassc
      2 output-sass/sass/perl-libsass
      2 output-sass/sass/language
      1 output-sass/sass/node-sass-middleware
      1 output-sass/sass/libsass.com

lmk and I can PR fixes for them with a single command