This repository has been archived by the owner on Nov 13, 2022. It is now read-only.
[Please Review] Automated Upgrade Of fastpages Template #143
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of Changes
Moved various files under
_fastpages_docs
in order to make the repo more organized, there was too many files in the root.Setup A Mechanism To Automatically Upgrade The Repository.
Overview of Automated Steps
Step 1: Open Issue
Users will be able to open an issue from this issue template:
Step 2: Wait 15 Seconds For Issue Comment
The user must not edit the title of the Issue, and proceed to opening the issue from the above template. When the issue is opened, a Pull Request is triggered that fetches the latest version of a subset of fastpages files ( basically everything except certain config files and blog post content ).
Actions then makes a comment with a link to the PR in the issue:
Step 3: Navigate to the PR
The user is presented with a PR that looks like this
Step 4: Review the PR and Merge
Things I would appreciate a review on
@jph00 @xnutsive
_upgrade_pr.md
Some notes: This is far easier than trying to merge upstream changes into your template because:
Feedback is very appreciated.