Connect the dev branch to dev-staging. We will continue the same QA process as before, but we will push to dev-staging and then thoroughly QA every week or so and make sure that all new features are working together, and no new bugs have appeared before merging to master. This can eventually be part of a regular release cycle, although we don't need to go that far just yet.
What are the steps for a QA tester to test this pull request?
Issue ticket number and link
Screenshots and/or video
Checklist before requesting a review
[ ] I have performed a self-review of my code
[ ] I am not adding any irrelevant code or assets
[ ] I am only including the changes needed to implement the change
[ ] I have playtested and intentionally tried to find error cases but couldn't
Describe your changes
Connect the dev branch to dev-staging. We will continue the same QA process as before, but we will push to dev-staging and then thoroughly QA every week or so and make sure that all new features are working together, and no new bugs have appeared before merging to master. This can eventually be part of a regular release cycle, although we don't need to go that far just yet.
What are the steps for a QA tester to test this pull request?
Issue ticket number and link
Screenshots and/or video
Checklist before requesting a review