Not having it is causing PR tests to temporarily show a failed test, as the Jekyll build needs to be on a site with Github Pages active.
Put differently, any push (even on forks) would result in the Jekyll workflow failing. We could leave the Linter workflow untouched, but it is changed for consistency in case the Linter workflow is expanded in scope.
Not having it is causing PR tests to temporarily show a failed test, as the Jekyll build needs to be on a site with Github Pages active.
Put differently, any push (even on forks) would result in the Jekyll workflow failing. We could leave the Linter workflow untouched, but it is changed for consistency in case the Linter workflow is expanded in scope.
Also fixes #121