The brownouts are scheduled for the following dates and times: To ensure all affected customers are aware of this change, during two scheduled brownouts, we will temporarily suspend redirection of Pages sites from *. If, however, your site still receives traffic through a redirect from *., after Apthat URL will stop working. If you’ve configured a custom domain for your Pages site or you directly access your site on *.github.io, you will not be affected by this change. We are taking this action to further protect overall. After April 15, 2021, we will stop doing this redirection. On April 5, 2013, we deprecated the *. domain for the Pages sites and started redirecting all traffic to the new location.
Today, we serve all GitHub Pages sites from the *.github.io domain, but before 2013 we used the *. domain. For now these actions are designed to be used in the generated workflow, however, starting early next year we will introduce some additional changes that will enable you to take advantage of them.īeginning April 15, 2021, we will stop redirecting GitHub Pages sites from *. to the *.github.io domain. You may notice this workflow uses some new actions actions/pages-deploy, and actions/jekyll-build-pages.
Github pages generator#
However, in the future this will enable us to give you the ability to fully customize your pages build and deployment workflow to use any static site generator you want without having to push the build output to a special branch of the repository. The initial benefit of this change is enabling you to see your build logs and any errors that may occur which has been a long standing issue for Pages users. As the name suggests, it builds and deploys your pages site. This workflow is automatically triggered when you push to the branch configured for GitHub Pages in your repository. Today you will begin to see a new workflow running called pages build and deployment in your public GitHub Pages repositories.
0 kommentar(er)
