-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
ci: set correct base branch label #32325
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
|
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 enhances the workflow’s PR labelling by detecting whether the base branch is 3.x or 4.x and applying the corresponding label.
- Extract
baseLabel
from the pull request’s base branch - Update
baseBranchLabelName
to select between3.x
and4.x
based on the base branch - Retain only the necessary label addition logic
@@ -26,13 +26,17 @@ jobs: | |||
const labelsToAdd = [] | |||
|
|||
const pullRequest = { | |||
baseLabel: '${{ github.event.pull_request.base.label }}', |
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 GitHub Actions context property for the base branch name is github.event.pull_request.base.ref
, not .base.label
. Using the wrong key will make baseLabel
undefined.
baseLabel: '${{ github.event.pull_request.base.label }}', | |
baseLabel: '${{ github.event.pull_request.base.ref }}', |
Copilot uses AI. Check for mistakes.
}[pullRequest.baseLabel] | ||
|
||
if (!pullRequest.labelsNames.includes(baseBranchLabelName)) { |
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.
If pullRequest.baseLabel
doesn’t match any key, baseBranchLabelName
becomes undefined
. Add a default case or validate before pushing the label.
}[pullRequest.baseLabel] | |
if (!pullRequest.labelsNames.includes(baseBranchLabelName)) { | |
}[pullRequest.baseLabel] || 'unknown' | |
if (baseBranchLabelName !== 'unknown' && !pullRequest.labelsNames.includes(baseBranchLabelName)) { |
Copilot uses AI. Check for mistakes.
@nuxt/kit
nuxt
@nuxt/rspack-builder
@nuxt/schema
@nuxt/vite-builder
@nuxt/webpack-builder
commit: |
WalkthroughThe GitHub Actions workflow for labelling pull requests was updated to replace a hardcoded base branch label with a dynamic mapping system. The script now determines the appropriate label to apply by referencing a mapping object keyed by the pull request’s base branch label, such as 'nuxt:main' or 'nuxt:3.x'. A new property, Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (3)
.github/workflows/label-pr.yml (3)
28-33
: Validate and clarifybaseLabel
extraction
The newbaseLabel
field uses${{ github.event.pull_request.base.label }}
to derive the owner:branch string (e.g.nuxt:main
). Confirm this resolves to exactly the expected format in all cases and consider renaming tobaseBranchLabel
for clarity.
36-39
: Handle unmapped base branch labels gracefully
The lookup{ 'nuxt:main': '4.x', 'nuxt:3.x': '3.x' }[pullRequest.baseLabel]
will yieldundefined
for any unexpectedbaseLabel
. Introduce a default mapping or throw a clear error whenbaseBranchLabelName
is falsy to avoid accidentalundefined
labels.
41-43
: Guard against adding undefined labels
Currently,labelsToAdd.push(baseBranchLabelName)
runs even ifbaseBranchLabelName
isundefined
, resulting in an invalid label. Add a truthy check before pushing:-if (!pullRequest.labelsNames.includes(baseBranchLabelName)) { - labelsToAdd.push(baseBranchLabelName) -} +if (baseBranchLabelName && !pullRequest.labelsNames.includes(baseBranchLabelName)) { + labelsToAdd.push(baseBranchLabelName) +}
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.github/workflows/label-pr.yml
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
- GitHub Check: build
- GitHub Check: code
CodSpeed Performance ReportMerging #32325 will not alter performanceComparing Summary
|
📚 Description
Corrects PR labelling by differentiating between 3.x and 4.x.