Migrate foundation website to Hugo #5
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* basic lift and shift over to Hugo * Add a Hugo publish workflow
lemmy
approved these changes
Apr 23, 2024
Thank you! A couple of questions for you @lemmy: do you prefer to have the reviewer merge or would you like me to? And do you have a preference towards rebase & merge or squash & merge? (I tend towards squash & merge just out of habit.) |
|
@juliaferraioli Please do as you see fit. :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
.gitignoreappropriate for the site/repoREADMEwith new file structureI realize that this is a big change in one pull request but I don't think there's a graceful way to break it up. You can preview the site live (deployed through the workflow) at my fork.