nx
Nx
GitHub
Nx
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
Nx
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
GitHub
Nx
Workspace
Succeeded
36851
3b7f6b20 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.
by Craigory C...
C
Succeeded
36851
3b7f6b20 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.
by Craigory C...
C
Canceled
36851
3b7f6b20 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.
by Craigory C...
C
Succeeded
36851
07857602 chore(repo): add PR stats and ages to weekly issue report The weekly Slack report now carries a second table with pull request data per scope label (open, created / merged / closed since the last report, average and p95 age of open PRs), and the issue table gains average and p95 age columns. Both tables start with Everything and Unscoped rows, which were missing before. PRs come from the same issues endpoints the scraper already paginates; they were being filtered out. Merged / closed PRs are re-checked against merged_at / closed_at because the endpoint's `since` filters on updated_at. The message is now one Slack section block per table chunk to stay under the 3000 character block limit, with the table header repeated in continuation chunks. Scope rows with no activity in a table are omitted, a missing previous value renders no delta instead of a delta from zero, and the footer links to the nx package health page on npm-burst.
by Craigory C...
C
Succeeded
36851
07857602 chore(repo): add PR stats and ages to weekly issue report The weekly Slack report now carries a second table with pull request data per scope label (open, created / merged / closed since the last report, average and p95 age of open PRs), and the issue table gains average and p95 age columns. Both tables start with Everything and Unscoped rows, which were missing before. PRs come from the same issues endpoints the scraper already paginates; they were being filtered out. Merged / closed PRs are re-checked against merged_at / closed_at because the endpoint's `since` filters on updated_at. The message is now one Slack section block per table chunk to stay under the 3000 character block limit, with the table header repeated in continuation chunks. Scope rows with no activity in a table are omitted, a missing previous value renders no delta instead of a delta from zero, and the footer links to the nx package health page on npm-burst.
by Craigory C...
C
Previous
Next