Skip to content

Add issue: tracking field to 4 near-ready A/B experiments - #55103

Merged
pelikhan merged 2 commits into
mainfrom
copilot/deep-report-add-issue-tracking-field
Aug 23, 2026
Merged

Add issue: tracking field to 4 near-ready A/B experiments#55103
pelikhan merged 2 commits into
mainfrom
copilot/deep-report-add-issue-tracking-field

Conversation

Copilot AI commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

0 of 44 workflows running A/B experiments declared a tracking issue: field in their experiments: frontmatter, so ready/significance/guardrail findings only ever posted to the ephemeral daily-experiment-report discussion instead of a durable, linkable issue. This addresses the 4 highest-value experiments flagged as the best starting point.

Findings

  • daily-security-red-team.md and ci-coach.md already declared issue: 31673 / issue: 32335 — no change needed.
  • daily-safe-output-optimizer.md and test-quality-sentinel.md were missing the field.

Changes

  • Added issue: 38094 to the log_fetch_strategy experiment in daily-safe-output-optimizer.md, linking to its originating [ab-advisor] Experiment campaign for daily-safe-output-optimizer issue.
  • Added issue: 43530 to the model_size experiment in test-quality-sentinel.md, linking to its originating [ab-advisor] Experiment campaign for test-quality-sentinel issue.
  • Recompiled lockfiles to reflect the frontmatter changes.
experiments:
  model_size:
    variants: [claude-haiku-4.5, claude-sonnet-4.6]
    ...
    start_date: "2026-07-05"
    issue: 43530

Each issue: value points to the real, pre-existing campaign issue that originally proposed the experiment (per ADR-29618 convention), rather than a newly minted issue.

…lity-sentinel experiments

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI changed the title [WIP] Add tracking issue field to 4 near-ready A/B experiments Add issue: tracking field to 4 near-ready A/B experiments Aug 23, 2026
Copilot AI requested a review from pelikhan August 23, 2026 14:56
@pelikhan
pelikhan marked this pull request as ready for review August 23, 2026 14:58
Copilot AI balanced review requested due to automatic review settings August 23, 2026 14:58
@pelikhan
pelikhan merged commit 5e604a0 into main Aug 23, 2026
@pelikhan
pelikhan deleted the copilot/deep-report-add-issue-tracking-field branch August 23, 2026 14:58

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Links two active A/B experiments to their verified campaign issues, enabling durable reporting by the experiment-report workflow.

Changes:

  • Added tracking issues #38094 and #43530.
  • Regenerated experiment specifications and metadata hashes.
Show a summary per file
File Description
.github/workflows/daily-safe-output-optimizer.md Links the log-fetch experiment to #38094.
.github/workflows/daily-safe-output-optimizer.lock.yml Propagates the tracking issue into generated output.
.github/workflows/test-quality-sentinel.md Links the model-size experiment to #43530.
.github/workflows/test-quality-sentinel.lock.yml Propagates the tracking issue into generated output.

Review details

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

  • Files reviewed: 4/4 changed files
  • Comments generated: 0
  • Review effort level: Balanced

@github-actions

Copy link
Copy Markdown
Contributor

🎉 This pull request is included in a new release.

Release: v0.87.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[deep-report] Add issue: tracking field to 4 near-ready A/B experiments

3 participants