IMPORTANT:
Github Actions and workflow processes should be assigned to your development team who will review and fixes the notifications visible on the deployment logs. Once all log items are reviewed and fixed by your development team, the StagingPro code deployments will be successful.
...
Q7. Can you explain how version control is managed within BigCommerce Staging Proworks for StagingPro with multiple development teams as part of existing CI/CD pipelines?
A7. When you successfully configure the GitHub integration on your StagingPro tenant, your GIT commits will be visible on the ‘Code Deployment’ tab which shows you your displays incremental version numbers.
Q8. What best practices do you recommend for managing version control with multiple development teams?
A8. Refer
| Anchor | ||
|---|---|---|
|
How can BigCommerce Staging Pro be integrated with our existing CI/CD pipelines? Are there any specific tools or platforms it aligns with best?
How does it work with Rewind?
What are the most common use cases we should be aware of and develop proficiency in?The code branches are created i) per environment ii) per channel and iii) per repo team member. Refer the ‘StagingPro Git Branch workflow’ section of this document. Under Settings > Status Notifications you can enable the Deployment Notifications checkbox for team notifications through i) Email ii) Teams and iii) Slack for shared visibility and effective collaboration.