-
Notifications
You must be signed in to change notification settings - Fork 257
Add github workflow to sync main into next #2522
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: next
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds an automated GitHub workflow to keep the main and next branches in sync by automatically creating pull requests when changes are pushed to main. The workflow includes conflict detection, issue creation for manual resolution, and auto-merge capabilities to streamline branch management.
- Implements automated sync from main to next branch via GitHub Actions
- Adds comprehensive conflict handling with fallback issue creation
- Includes a linting script for workflow validation
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
File | Description |
---|---|
.github/workflows/sync-main-to-next.yml |
Main workflow implementing automated branch sync with conflict detection and PR creation |
scripts/lint-workflows.sh |
Shell script for validating GitHub Actions workflows using actionlint |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.
owner, | ||
repo, | ||
pull_number: pr.data.number, | ||
team_reviewers: ["bugsnag-dev"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The team name 'bugsnag-dev' appears to be hardcoded and specific to another organization. This should be parameterized or updated to match the actual team structure of this repository.
Copilot uses AI. Check for mistakes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated to platforms-javascript-developers
and created a matching team under the platforms team
7e436f4
to
21b9d05
Compare
As discussed IRL, I think we should look at turning this into a common workflow that's maintained in a single location. |
Goal
This PR adds an automated GitHub workflow to keep the main and next branches in sync, ensuring that all changes pushed to main are automatically propagated to the next branch.
Replicates the smartbear-mcp sync workflow