Function detectChannelMoves

packages/bumpy/src/commands/ci.ts:950–976

* Bump file IDs added to `.bumpy/ /` by the push that triggered this run. * * This is the channel publish trigger: merging the release PR moves files into the * channel dir; ordinary feature merges don't touch it. Re-running on the same push is * idempotent — packages already published f

(rootDir: string, channel: ResolvedChannel)

 * gitHead recorded on the registry.
 */
function detectChannelMoves(rootDir: string, channel: ResolvedChannel): string[] {
  const range = getPushEventRange();
  let diffRange: string;
  if (range) {
    diffRange = `${range.before}..${range.after}`;
  } else {
    if (!tryRunArgs(['git', 'rev-parse', '--verify', 'HEAD^'], { cwd: rootDir })) {
      log.warn(
        'Cannot diff against the previous commit (shallow clone?) — channel publish trigger unavailable.\n' +
          '  Use `fetch-depth: 0` in your checkout step, or run `bumpy publish` manually on the channel branch.',
      );
      return [];
    }
    diffRange = 'HEAD^..HEAD';
  }

  // --no-renames so file moves into the channel dir show up as additions
  const out = tryRunArgs(
    ['git', 'diff', '--name-only', '--diff-filter=A', '--no-renames', diffRange, '--', `.bumpy/${channel.name}/`],
    { cwd: rootDir },
  );
  if (!out) return [];
  return out
    .split('\n')
    .filter((f) => f.endsWith('.md') && !f.endsWith('README.md'))
    .map((f) => f.split('/').pop()!.replace(/\.md$/, ''));
}

/**
 * CI release on a channel branch. Two independent steps, both of which can run