Comparing v4.1.1...v4.1.2 · actions/checkout (original) (raw)

Commits on Feb 21, 2024

1. Configuration menu
   Browse the repository at this point in the history
2. Explicitly disable sparse checkout unless asked for (#1598)
   When a worktree is reused by actions/checkout and the first time sparse checkout was enabled, we need to ensure that the second time it is only a sparse checkout if explicitly asked for. Otherwise, we need to disable the sparse checkout so that a full checkout is the outcome of this Action.

Details

• If no sparse-checkout parameter is specified, disable it
  This should allow users to reuse existing folders when running
  actions/checkout where a previous run asked for a sparse checkout but
  the current run does not ask for a sparse checkout.
  This fixes #1475
  There are use cases in particular with non-ephemeral (self-hosted) runners where an
  existing worktree (that has been initialized as a sparse checkout) is
  reused in subsequent CI runs (where actions/checkout is run without
  any sparse-checkout parameter).
  In these scenarios, we need to make sure that the sparse checkout is
  disabled before checking out the files.

Also includes:

• npm run build
• ci: verify that an existing sparse checkout can be made unsparse
• Added a clarifying comment about test branches.
• test-proxy now uses newly-minted test-ubuntu-git container image from ghcr.io

Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de
Co-authored-by: John Wesley Walker III 81404201+jww3@users.noreply.github.com

Configuration menu
Browse the repository at this point in the history