Update README.md to add instructions for how to add workflow to automate deployment on pushes to master branch #198
Conversation
This file contains hidden or 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
…deploy command on pushes to master
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.
I added an optional step 10 in the README.md that describes how to set up a GitHub workflow to automate the deployment process. This workflow triggers the
npm run deploycommand to update thegh-pagesbranch whenever changes are pushed to themasterbranch, ensuring the deployed website on GitHub Pages is always up to date.I initially wrote this workflow for personal use to avoid manual update of GitHub pages. I believe it will be helpful for others who want their changes on the main branch to be automatically reflected on GitHub Pages without additional steps.