[flowcool]

Behavior

Follow-up to #133. That PR removed the labeled trigger from PR release labels on the assumption that the workflow re-triggered on its own label writes. Labels written with GITHUB_TOKEN never trigger workflows, so the removal saved nothing and dropped the Release impact re-check when breaking-change or compat is added by hand (finding from the Pullfrog review of the sibling boursedirect-sync PR). This restores the original trigger list.

Release impact

None. CI only.

Verification

• Command: git diff origin/main~1 -- .github/workflows/pr-release-labels.yml before ci: cut CI and review-bot cost; one PR per change #133
• Expected result: trigger list identical to the pre-ci: cut CI and review-bot cost; one PR per change #133 version.
• Observed result: types: [opened, edited, reopened, labeled].

AI assistance

Prepared by Claude Code (Opus 5.5).

🤖 Generated with Claude Code

https://claude.ai/code/session_01EQXdcx49Pi5uQErd6kDEKs

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: flowcool/ghostfolio-degiro-sync
• Branch: ci/restore-labeled
• File: .coderabbit.yaml
• Commit: 8680555
• Layers: Repository YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: dac72a83-3f34-4d21-b999-5c8e64d3f1a1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[pullfrog]

✅ No new issues found.

Reviewed changes

Reviewed the single-commit diff to .github/workflows/pr-release-labels.yml.

• Restored labeled trigger — pull_request.types is back to [opened, edited, reopened, labeled], so a hand-added breaking-change or compat label re-runs the Release impact check.

Verified against scripts/label_pr_release.py: main() builds current from pr["labels"] in the event payload, which on a labeled event includes the newly added label, so the impact warning evaluates correctly. Labels the script writes with GITHUB_TOKEN do not trigger workflows, so there is no re-trigger loop. The script is advisory and always returns 0, and the job keeps minimal permissions with a pinned checkout, so the change adds no required-check or secret exposure concerns.

  ^{｜ View workflow run ｜ Using claude-sonnet-5-5 ｜ 𝕏}