Run details

NxWorkspace

CI Pipeline Executions
- Current executionSucceeded
  weekly-slack-report-pr-data-6e2dd3e0
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

Sign in

chore(repo): lay out the weekly issue report with block kit and add a dry run The Slack message now uses a header block for the title, a context block for the notes, one section per unlabeled-items link (the encoded label filters run over 1500 characters each, so two in one section breaks the 3000 character limit), a divider before each table, and a context block for the footer link. workflow_dispatch gets a dry_run input, on by default, that skips the Slack message and the cached-data upload. A manual run would otherwise overwrite the artifact the next scheduled run diffs against, moving its "since" window to the day of the test. The job summary is still written.

nx run-many -t check-imports check-lock-files check-codeowners --parallel=1 --no-dte

Succeeded

4 CPU cores

read-write access token used

a690eb2e36851

Get faster results

Learn how to enable distribution.

Atomizer enabled

1 group of tasks optimized.

Machine

4 cores · 15.61 GB

CPU (avg / max)

68.3% / 137.14%

Memory (avg / max)

1.15 GB / 1.36 GB

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

NxWorkspace