Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe PR evaluation service now aggregates exclude-mode labels from create rules (global and per-product), case-insensitively deduplicates them, and produces a comma-joined Sequence Diagram(s)mermaid 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches✨ Simplify code
Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
src/services/Elastic.Changelog/Evaluation/ChangelogPrEvaluationService.cs (1)
220-221: Discard assignment is unnecessary.
HashSet.Addreturn value doesn't need explicit discard.Suggested simplification
if (createRules is { Mode: FieldMode.Exclude, Labels.Count: > 0 }) { foreach (var label in createRules.Labels) - _ = labels.Add(label); + labels.Add(label); } if (createRules.ByProduct is { Count: > 0 }) { foreach (var (_, productRules) in createRules.ByProduct) { if (productRules is { Mode: FieldMode.Exclude, Labels.Count: > 0 }) { foreach (var label in productRules.Labels) - _ = labels.Add(label); + labels.Add(label); } } }Also applies to: 230-231
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/services/Elastic.Changelog/Evaluation/ChangelogPrEvaluationService.cs` around lines 220 - 221, The discard assignment is unnecessary when calling HashSet.Add; inside the loops that iterate createRules.Labels (the block using labels.Add) remove the "_ =" discard and call labels.Add(label) directly; apply the same change to the similar loop at the other occurrence (the one around lines referencing createRules.Labels again) so both uses of HashSet.Add omit the redundant discard.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@src/services/Elastic.Changelog/Evaluation/ChangelogPrEvaluationService.cs`:
- Around line 220-221: The discard assignment is unnecessary when calling
HashSet.Add; inside the loops that iterate createRules.Labels (the block using
labels.Add) remove the "_ =" discard and call labels.Add(label) directly; apply
the same change to the similar loop at the other occurrence (the one around
lines referencing createRules.Labels again) so both uses of HashSet.Add omit the
redundant discard.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: cb8c87b6-5f56-49e1-b75f-951a9e8c7c15
📒 Files selected for processing (1)
src/services/Elastic.Changelog/Evaluation/ChangelogPrEvaluationService.cs
Mpdreamz
left a comment
There was a problem hiding this comment.
Lgtm, maybe add a quick unit test?
* Fix redirect tests * Remove changelog redirects implemented elsewhere
) Elasticsearch Serverless now defaults semantic_text to Jina, making the explicit Jina sub-fields redundant and the ELSER inference ID unnecessary. This removes both inference ID constants, all .jina field mappings, and lets semantic_text fields use the platform default. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Made with ❤️️ by updatecli Co-authored-by: elastic-observability-automation[bot] <180520183+elastic-observability-automation[bot]@users.noreply.github.com>
The deploy apply command used RealRead which lacks AllowedSpecialFolder.Temp, causing ScopedFileSystemException when AwsS3SyncApplyStrategy stages files in /tmp/ for S3 upload. Switch to RealWrite which permits temp directory access. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
… PRs (#2971) Add IsAotCompatible to 12 library projects referenced by docs-builder so Roslyn's trim/AOT analyzers (IL2026/IL3050) run during regular builds. This catches AOT issues at compile time, removing the need for the expensive native ILC publish step on pull requests. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* HTML: Omit version meta tags for versionless pages Versionless pages (serverless, cloud, etc.) were rendering the sentinel value 99999.0+ in product_version and DC.identifier meta tags. Now these tags are omitted entirely when the page's versioning system is versionless. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * HTML: Restore required modifier on CurrentVersion property Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…3025) * Layout: Adapt to static elastic-nav by making secondary nav sticky The global elastic-nav.js (v2026-03) changed the header from fixed to static positioning. This makes the secondary docs nav sticky at the top and simplifies --offset-top to match its height. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Layout: Only make secondary nav sticky on md+ viewports On mobile the sticky secondary nav takes too much vertical space. Keep it static on small screens (--offset-top: 0) and only sticky on md+ where it provides persistent navigation. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * chore: Upgrade lodash to 4.18.x to fix high severity vulnerabilities Fixes code injection via _.template (GHSA-r5fr-rjxr-66jc) and prototype pollution via _.unset/_.omit (GHSA-f23m-r3pf-42rh). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Layout: Add bottom border to secondary nav The visual separator was coming from #main-container's border-top, which scrolls away. Adding border-b to the nav itself keeps the line visible while sticky. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Layout: Remove border-top from main-container The secondary nav now has border-b, so the main-container border-t was causing a double border. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…-label # Conflicts: # tests/Elastic.Changelog.Tests/Evaluation/ChangelogPrEvaluationServiceTests.cs
This pull request enhances the PR evaluation process in the
ChangelogPrEvaluationServiceby adding support for collecting and outputting labels that cause a PR to be skipped due to exclusion rules. The main focus is on improving traceability and diagnostics when PRs are skipped based on label configurations.Key changes:
Skip label handling and output:
CollectExcludeLabels, which gathers all unique exclude-mode labels from both global and per-productCreateRules. This method returns a comma-separated string of labels ornullif none are configured.EvaluatePrto collect skip labels and pass them to the output when a PR is skipped due to all products being blocked by label rules.SetOutputsmethod to accept an optionalskipLabelsparameter and output it asskip-labelswhen present. [1] [2]