This might be overkill for the scope of our project, but would introducing a QA branch make sense?
I’m not suggesting we host a separate QA environment, but rather use a qa branch as an intermediate step between your_dev_branch → qa → main to help catch issues before merging into main. Team members could check out the branch, test the feature, and then we can merge to main once it’s been validated
Let me know
@JadHay8
This might be overkill for the scope of our project, but would introducing a QA branch make sense?
I’m not suggesting we host a separate QA environment, but rather use a qa branch as an intermediate step between your_dev_branch → qa → main to help catch issues before merging into main. Team members could check out the branch, test the feature, and then we can merge to main once it’s been validated
Let me know
@JadHay8