Repository navigation

feat: save the baseline to a branch of its own, and generate the review's base in a step of its own - #143

Open

ivanmilevtues wants to merge 13 commits into

mainfrom

refactor/review-baseline-pipeline

Commits on Oct 7, 2026
- feat: report how the review base was built
  
  Svilen-Stefanov
  and
  claude
  committed
  7a091f5
- fix: count merges as catch-up and never call an unknown base exact
  
  Svilen-Stefanov
  and
  claude
  committed
  74d36ce
Commits on Oct 9, 2026
- refactor: report the base analysis as reused, incremental or full
  
  Svilen-Stefanov
  and
  claude
  committed
  6b46ac3
- feat: catch up the review base from the nearest saved ancestor
  
  Svilen-Stefanov
  and
  claude
  committed
  3ca8dc1
- feat: save the diagram to an analysis branch of its own
  
  Svilen-Stefanov
  and
  claude
  committed
  7a65300
Commits on Oct 10, 2026
- feat: name sync inputs for what they do, and move base timings to telemetry
  
  ivanmilevtues
  and
  claude
  committed
  608b37d
- refactor: split the review into baseline and head steps, and analyze one commit at a time
  
  ivanmilevtues
  and
  claude
  committed
  1fb65b1
- ci: run review and sync from one CodeBoarding workflow
  
  ivanmilevtues
  and
  claude
  committed
  17cd1e8
- fix: keep analysis credentials for the review's second analysis step
  
  ivanmilevtues
  and
  claude
  committed
  1560c90
- fix: let sync read the analyses reviews save
  
  ivanmilevtues
  and
  claude
  committed
  7776d20
- feat: keep the analysis on codeboarding_analysis_branch, and fail instead of degrading silently
  
  ivanmilevtues
  and
  claude
  committed
  6597352
- fix: name the branch the run is on when target_branch points elsewhere
  
  ivanmilevtues
  and
  claude
  committed
  c4820ee
Commits on Oct 11, 2026
- feat: choose where the analysis lives, and keep one branch's analysis per repository
  
  ivanmilevtues
  and
  claude
  committed
  381a0c4

Navigation Menu

Repository navigation

feat: save the baseline to a branch of its own, and generate the review's base in a step of its own - #143

feat: save the baseline to a branch of its own, and generate the review's base in a step of its own#143
ivanmilevtues wants to merge 13 commits into
mainfrom
refactor/review-baseline-pipeline

Commits on Oct 7, 2026

feat: report how the review base was built

fix: count merges as catch-up and never call an unknown base exact

Commits on Oct 9, 2026

refactor: report the base analysis as reused, incremental or full

feat: catch up the review base from the nearest saved ancestor

feat: save the diagram to an analysis branch of its own

Commits on Oct 10, 2026

feat: name sync inputs for what they do, and move base timings to telemetry

refactor: split the review into baseline and head steps, and analyze one commit at a time

ci: run review and sync from one CodeBoarding workflow

fix: keep analysis credentials for the review's second analysis step

fix: let sync read the analyses reviews save

feat: keep the analysis on codeboarding_analysis_branch, and fail instead of degrading silently

fix: name the branch the run is on when target_branch points elsewhere

Commits on Oct 11, 2026

feat: choose where the analysis lives, and keep one branch's analysis per repository