Skip to content
This repository has been archived by the owner on Nov 13, 2022. It is now read-only.

Latest commit

 

History

History
74 lines (45 loc) · 4.36 KB

UPGRADE.md

File metadata and controls

74 lines (45 loc) · 4.36 KB
Raw

Upgrading fastpages

For fastpages repos that are older than December 1st, 2020 the only way to upgrade is to create a brand-new fastpages repo and copy your blog post files into it. This is because of breaking changes that were made to GitHub Actions around that time.

There are two ways to upgrade fastpages. One is an automated way that assumes you have made no changes to the HTML of your site. Alternatively, you may upgrade manually and determine which changes to accept or reject. For most people we recommend upgrading fastpages automatically.

Automated Upgrade

  • This method is appropriate for those who have not customized the HTML of their site.
  • If you are unsure, try the Automated approach and review which files are changed in the automated PR to see if this appropriate for you.

Step 1: Open An Issue With The Upgrade Template.

  • Open a new issue in your repository, and push the "Get Started" button for the [fastpages] Automated Upgrade Issue template, which looks like this:

    • IF YOU DON'T SEE THIS: you have an older version of fastpages and you must manually upgrade once to get this new functionality.

Step 2: Click Submit new issue

  • Be careful not to change anything before clicking the button.

Step 3: A Link to Pull Request Will Appear

  • This issue will trigger GitHub to open a PR making changes to your repository for the upgrade to take palce. A comment with the link to the PR will be made in the issue, and will look like this:

    It is possible that you might receive an error message instead of this command. You can follow the instructions in the comment to troubleshoot the issue. Common reasons for receiving an error are:

    • You are up to date, therefore no upgrade is possible. You will see an error that there is "nothing to commit".
    • You already have a PR from a previous upgrade open that you never merged.

    Please ask on the forums if you have encounter another problem that is unclear.

Step 4: Review & Merge PR

  • Ensure that you read the instructions in the PR carefully. Furthermore, carefully review which files will be changed to determine if this interferes with any customizations you have mades to your site. When ready, select Merge pull request.
  • If the PR is making undesired changes to files you can use the manual upgrade approach instead.

Manual Upgrade

Easy Way (Recommended)

Create a new repo with the current fastpages template by following the setup instructions in the README, and copy all of your blog posts from _notebooks, _word, and _posts into the new template. This is very similar to what the automated process is doing.

Advanced

  • This method is appropriate for those who made customizations to the HTML of fastpages.
  • You must proceed with caution, as new versions of fastpages may not be compatible with your customizations.
  • You can use git to perform the upgrade by following this approach instead. A step-by-step companion to this stack overflow post with screenshots is written up here.
  • Be careful to not duplicate files, as files in fastpages have been reorganized several times.

Additional Resources