Updated the Github Actions to deploy a test version of the site to a … #35
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.
Key Changes
deploy_staging job: I made this new job making sure it handles the deployment of any branch to the
/staging
folder. It's triggered by theworkflow_dispatch
event, meaning it can be run manually from the GitHub Actions tab.destination_dir: staging: In the
deploy_staging
step, I set thedestination_dir
option tostaging
, so the files will be deployed to the/staging
folder on GitHub Pages.Manual trigger: Since the
deploy_staging
job runs only onworkflow_dispatch
, it won’t interfere with regular deployments to the main branch.How to Trigger:
From research, i discovered that the workflow can be manually triggered by navigating to the Actions tab on GitHub, selecting the appropriate workflow, and running it for a desired branch. This will deploy the changes to a
/staging
folder on GitHub Pages.This setup allows you to have two separate deployments: one for the main branch (direct deployment to GitHub Pages) and one for testing in a
/staging
folder.