-
Notifications
You must be signed in to change notification settings - Fork 89
Vvolkgang/label cron workflows #2267
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
3720097 to
efdc231
Compare
|
Great job! No new security vulnerabilities introduced in this pull request |
|
Claude finished @vvolkgang's task in 1m 24s —— View job Code Review SummaryPR: #2267 - Vvolkgang/label cron workflows OverviewThis PR modifies the SDLC PR labeling workflow (
Findings
❌ CriticalMissing Python script invocation (line 87) The
|
efdc231 to
0b50300
Compare
| _PR_LABELS=$(gh pr view "$_PR_NUMBER" --json labels --jq '.labels[].name') | ||
| fi | ||
| echo "🔍 Current PR labels: $_PR_LABELS" | ||
| echo "🔍 Labeling PR #$_PR_NUMBER with mode: $_LABEL_MODE and dry-run: $_DRY_RUN and current PR labels: $_PR_LABELS..." |
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.
❌ CRITICAL: The python3 .github/scripts/label-pr.py invocation was removed. This workflow will now log information but never actually apply any labels to PRs, completely breaking the labeling functionality.
The previous implementation called:
python3 .github/scripts/label-pr.py "$_PR_NUMBER" "$_LABEL_MODE" "$_DRY_RUN"This line needs to be restored, likely with the additional _PR_LABELS parameter if the intent is to pass existing labels to the script.
| if [ -z "$_PR_LABELS" ] || [ "$_PR_LABELS" = "null" ] || [ "$_PR_LABELS" = "[]" ]; then | ||
| echo "🔍 No current PR labels found, retrieving PR data for PR #$_PR_NUMBER..." | ||
| _PR_LABELS=$(gh pr view "$_PR_NUMBER" --json labels --jq '.labels[].name') | ||
| fi | ||
| echo "🔍 Current PR labels: $_PR_LABELS" |
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.
_PR_LABELS variable is fetched but never used. Based on the commit message "Keep existing labels", it appears the intent was to pass existing labels to the Python script so they can be preserved during labeling.
However, the Python script (label-pr.py) currently does not accept a labels parameter. If preserving existing labels is the goal, the script would need to be modified to accept and use this information.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2267 +/- ##
==========================================
- Coverage 85.88% 84.70% -1.18%
==========================================
Files 1760 2009 +249
Lines 150938 167804 +16866
==========================================
+ Hits 129628 142145 +12517
- Misses 21310 25659 +4349 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
0b50300 to
a8da81a
Compare
a8da81a to
4bd89bd
Compare

🎟️ Tracking
📔 Objective
📸 Screenshots
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:) or similar for great changes:memo:) or ℹ️ (:information_source:) for notes or general info:question:) for questions:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:) for suggestions / improvements:x:) or:warning:) for more significant problems or concerns needing attention:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt:pick:) for minor or nitpick changes