Prefer main when auto-merging into staging#1371
Conversation
Use merge -X theirs so rename and content conflicts no longer block the staging sync chain. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Pull requests must include at least one of the required labels: |
PR SummaryThis PR updates the GitHub Actions workflow responsible for merging changes from the main branch into staging. The merge step now uses a strategy that favors the main branch by running a merge with the '-X theirs' option. In case of merge conflicts, the script automatically resolves them by checking out the main branch's versions for the affected files, adding them, and committing the merge. This ensures that in the event of a conflict, the main branch's changes take precedence without manual intervention. Test Suggestions
|
Validate docs site✓ INFO: A live preview of the docs site is available — Open the preview |
Lighthouse check results✓ INFO: No site pages to audit in this PR. Commit SHA: 4d4609d |
Summary
Updates the Merge main into staging workflow so conflicts resolve in favor of
maininstead of failing and leavingstagingstuck.git merge -X theirs(onstaging,theirs=main)git checkout --theirsfor any paths Git still marks unmergedTest plan
mainstagingmainand confirm Merge main into staging succeeds without manual interventionMade with Cursor