-
Notifications
You must be signed in to change notification settings - Fork 640
Remove next-major branch references from workflows #7104
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: main
Are you sure you want to change the base?
Conversation
|
Co-authored-by: siddharthkp <1863771+siddharthkp@users.noreply.github.com>
| {id: 'main', name: 'main', trailingInfo: 'Default'}, | ||
| {id: 'next-major', name: 'next-major'}, | ||
| {id: 'changeset-release/main', name: 'changeset-release/main'}, | ||
| {id: 'changeset-release/next-major', name: 'changeset-release/next-major'}, |
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.
lol but sure
|
👋 Hi, this pull request contains changes to the source code that github/github depends on. If you are GitHub staff, we recommend testing these changes with github/github using the integration workflow. Thanks! |
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.
This looks good, well done!
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 removes all references to the deprecated next-major branch from the codebase. The next-major branch was previously used to collect changes for major releases, but this workflow is no longer followed and the remnants needed cleanup.
Key changes:
- Removed
next-majorbranch triggers from CI/CD workflows (ci.yml, reports.yml, release_canary.yml, release_candidate.yml) - Removed the entire
release-next-majorjob from the release workflow - Removed
next-majorandchangeset-release/next-majorbranch entries from SelectPanel2 test mock data
Reviewed Changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/ci.yml |
Removed next-major from push and merge_group branch triggers |
.github/workflows/reports.yml |
Removed next-major from push and merge_group branch triggers |
.github/workflows/release_candidate.yml |
Removed next-major from changeset-release branch triggers |
.github/workflows/release_canary.yml |
Removed next-major from branches-ignore list |
.github/workflows/release.yml |
Removed entire release-next-major job and associated configuration |
packages/react/src/experimental/SelectPanel2/mock-story-data.ts |
Removed next-major and changeset-release/next-major branch entries from test fixtures |
|
@copilot Can you perform this task again after merging main? |
Co-authored-by: siddharthkp <1863771+siddharthkp@users.noreply.github.com>
Done! Merged main into the PR branch (commit eb1bbe4). The workflows have been consolidated in main - |
|
@copilot Oof, that's not it. Revert last commit |
…y removed" This reverts commit eb1bbe4.
next-majorfrombranches-ignorein.github/workflows/release_canary.ymlnext-majorfrombranchestrigger in.github/workflows/ci.yml(2 occurrences)next-majorfrombranchestrigger in.github/workflows/release.ymlrelease-next-majorjob from.github/workflows/release.ymlchangeset-release/next-majorfrom branches in.github/workflows/release_candidate.ymlnext-majorfrombranchestrigger in.github/workflows/reports.yml(2 occurrences)next-majorbranches inpackages/react/src/experimental/SelectPanel2/mock-story-data.tsAll references to the deprecated
next-majorbranch have been successfully removed from the codebase. Thenext-majorbranch was previously used to collect changes for major releases, but this workflow is no longer followed.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.