You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to simplify things but also keep everything secure and accessible, here's my proposed deployment workflow:
staging is the main working branch, which is synced to the staging website. We use it to test changes.
When you need to test changes in the staging branch, you can SSH into the server and git pull to get the changes.
When everything is ready and needs to be deployed, create a PR to merge staging with production.
At this point git pull in the right directory will sync production branch on the server. production branch is protected.
We may automate step 4 using GitHub Actions to deploy code automatically once changes are made to the production branch. This will expedite the process and can also help reduce access to sensitive server credentials.
The text was updated successfully, but these errors were encountered:
In order to simplify things but also keep everything secure and accessible, here's my proposed deployment workflow:
staging
is the main working branch, which is synced to the staging website. We use it to test changes.staging
branch, you can SSH into the server andgit pull
to get the changes.staging
withproduction
.git pull
in the right directory will syncproduction
branch on the server.production
branch is protected.We may automate step 4 using GitHub Actions to deploy code automatically once changes are made to the
production
branch. This will expedite the process and can also help reduce access to sensitive server credentials.The text was updated successfully, but these errors were encountered: