Skip to content

Conversation

gingerbenw
Copy link
Member

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

Copy link

github-actions bot commented Aug 13, 2025

@bugsnag/browser bundle size diff

Minified Minfied + Gzipped
Before 47.11 kB 14.09 kB
After 47.11 kB 14.09 kB
± No change No change

code coverage diff

<temporarily disabled>

Generated by 🚫 dangerJS against 21b9d05

@gingerbenw gingerbenw marked this pull request as ready for review August 13, 2025 08:42
@gingerbenw gingerbenw requested a review from Copilot August 13, 2025 08:42
Copy link
Contributor

@Copilot Copilot AI left a 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"]
Copy link
Preview

Copilot AI Aug 13, 2025

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.

Copy link
Member Author

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

@twometresteve
Copy link
Contributor

As discussed IRL, I think we should look at turning this into a common workflow that's maintained in a single location.

@twometresteve twometresteve removed their request for review August 13, 2025 13:58
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.

3 participants