Aliaksandr a100d091a0 ci/eval: name the base branch in the performance comparison summary ... The performance comparison summary previously stated it compared against "its pull request base branch (e.g., 'master')" regardless of the actual base branch. Plumb the base branch classification computed in prepare.js through the eval workflow to the `compare` derivation so the summary names the real base branch (e.g. "staging-25.11"). The local `eval.full` helper defaults to "master", matching its touched-files convention. Assisted-by: claude-code with claude-opus-4-8[1m]-high		2026-06-17 01:08:45 +03:00
..
actions/checkout	github: Serialize git worktree initialization	2026-04-20 20:10:40 -04:00
ISSUE_TEMPLATE	.github/ISSUE_TEMPLATE: Mark 26.05 stable	2026-05-30 14:21:21 +02:00
workflows	ci/eval: name the base branch in the performance comparison summary	2026-06-17 01:08:45 +03:00
dependabot.yml	.github/dependabot.yml: set commit message prefix	2026-03-16 17:50:08 -04:00
labeler-development-branches.yml	workflows/bot: rename from labels	2025-11-01 15:24:09 +01:00
labeler-no-sync.yml	.github: Add release-26.05 CI config	2026-05-24 14:51:41 +02:00
labeler.yml	.github/labeler.yml: add staging-nixos to workflow backport	2026-05-30 11:00:00 +10:00
PULL_REQUEST_TEMPLATE.md	CONTRIBUTING.md: establish initial automation/AI/LLM policy	2026-05-11 23:12:40 +01:00
STALE-BOT.md
zizmor.yml	Reapply "ci: update pinned"	2026-04-04 16:13:11 -04:00