Skip to content

Test: enable destination rebase for copybara webdev sync#515

Closed
coreymartin wants to merge 1 commit intomainfrom
test/enable-destination-rebase
Closed

Test: enable destination rebase for copybara webdev sync#515
coreymartin wants to merge 1 commit intomainfrom
test/enable-destination-rebase

Conversation

@coreymartin
Copy link
Copy Markdown
Contributor

Summary

  • Removes --nogit-destination-rebase flag from the copybara sync to webdev
  • Temporarily enables the create-webdev-pr job on PRs so we can test the copybara flow without merging to main

Context

The --nogit-destination-rebase flag was originally added to avoid merge conflicts when copybara rebases onto webdev main. However, the conflicts were likely from CHANGELOG files, which only change in the public repo — so there shouldn't actually be conflicts during rebase.

Without this flag, copybara automatically rebases the sync commit onto current webdev main, which eliminates the stale PR branch problem we've been hitting (see lightsparkdev/webdev#25478).

Test plan

  • Open this PR and let the create-webdev-pr job run
  • Verify copybara successfully creates/updates the webdev sync PR with destination rebase enabled
  • Check that no merge conflicts occur during the rebase
  • If successful, merge this to enable destination rebase permanently

🤖 Generated with Claude Code

Remove --nogit-destination-rebase so copybara rebases the sync commit
onto current webdev main. This was originally disabled due to merge
conflicts, but those may have been from a one-time issue. If the rebase
succeeds, it eliminates the stale PR branch problem entirely.

Also temporarily enables the create-webdev-pr job on PRs (not just
push to main) so we can test the copybara flow without merging to main.
The "Reset develop to main" step is gated to push-only to avoid
destructive side effects on PR runs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coreymartin
Copy link
Copy Markdown
Contributor Author

Confirmed: destination rebase causes conflicts in js/package.json, js/packages/origin/CHANGELOG.md, and js/packages/origin/package.json. The --nogit-destination-rebase flag is still needed. Will address PR branch staleness on the webdev CI side instead.

@coreymartin coreymartin closed this Apr 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant