Johannes Schindelin aadec89964
Some checks failed
Build and Test / test (macos-latest) (push) Waiting to run
Build and Test / test (windows-latest) (push) Waiting to run
CodeQL / Analyze (javascript) (push) Failing after 7s
Build and Test / test-git-container (push) Failing after 8s
Build and Test / test-bypass-proxy (push) Failing after 41s
Check dist / check-dist (push) Failing after 1m16s
Build and Test / test (ubuntu-latest) (push) Failing after 1m34s
Licensed / Check licenses (push) Failing after 7m48s
Build and Test / test-proxy (push) Failing after 1h13m8s
Build and Test / build (push) Failing after 3h9m52s
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 https://github.com/actions/checkout/issues/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>
2024-02-21 13:56:19 +01:00
..