Add a New Workflow for Deploying the Master Branch to a Separate Website

[elnazzz95]

description:
Currently, the main branch is deployed to GitHub Pages, and we want to keep this deployment setup intact. However, we would like to deploy the master branch to a separate website for previewing or testing purposes.

Could we add a new GitHub Actions workflow (or similar deployment method) to automatically deploy the master branch to a different site (e.g., a staging environment or another GitHub Pages site)?

This way, we can keep the main as the production branch and have the master serve as a preview or testing site without any conflict.

[gmacario]

Could we add a new GitHub Actions workflow (or similar deployment method) to automatically deploy the master branch to a different site (e.g., a staging environment or another GitHub Pages site)?

I would also suggest another related use-case, which is to allow forks of this repository (for those like myself who do not have write access to https://github.com/Three-Buddy-Problem/exoplanet-quest-web) to be able to deploy the generated website to a different URL - in my case, something like https://gmacario.github.io/exoplanet-quest-web

Note: Depending on how you plan to implement the fix to this issue it might happen that my proposed use case will also be fulfilled, however I mentioned it explicitly since I can be helping for testing it