From 27bd8a52dee23f6e793bf5d3aeda65312bc58ed4 Mon Sep 17 00:00:00 2001 From: ALICE Action Bot Date: Mon, 21 Sep 2026 08:39:55 +0000 Subject: [PATCH] MegaLinter fixes --- .claude/commands/migrate-ccdb.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.claude/commands/migrate-ccdb.md b/.claude/commands/migrate-ccdb.md index 4f6bce9ab5d..509fd4a5d91 100644 --- a/.claude/commands/migrate-ccdb.md +++ b/.claude/commands/migrate-ccdb.md @@ -195,10 +195,10 @@ pre-existing behaviour — every distinct timestamp may yield a different object Pick it from the object's real validity, and only then: -| Object changes ... | Uniformity | Declare with | -| --- | --- | --- | -| within a run (calibrations, drift velocity) | timestamp (default) | `DECLARE_SOA_TIMESTAMPED_TABLE` | -| per run or per period (geometry, material, per-period calibrations) | `aod::BCs` / `aod::bc::RunNumber` | `DECLARE_SOA_UNIFORM_TABLE` | +| Object changes ... | Uniformity | Declare with | +|---------------------------------------------------------------------|-----------------------------------|---------------------------------| +| within a run (calibrations, drift velocity) | timestamp (default) | `DECLARE_SOA_TIMESTAMPED_TABLE` | +| per run or per period (geometry, material, per-period calibrations) | `aod::BCs` / `aod::bc::RunNumber` | `DECLARE_SOA_UNIFORM_TABLE` | Worked examples in the tree: `aod::TpcCalibCCDBObjects` keeps the timestamp default because the TPC drift velocity genuinely varies within a run; `aod::GeomCCDBObjects` and