checkout

Commit Graph

Author	SHA1	Message	Date
John Wesley Walker III	43045ae669	Disable `extensions.worktreeConfig` when disabling `sparse-checkout` (#1692 )	1 year ago
John Wesley Walker III	cd7d8d697e	Check git version before attempting to disable `sparse-checkout` (#1656 ) * Check git version before attempting to disable `sparse-checkout` * Bump `MinimumGitSparseCheckoutVersion` to 2.28 due to #1386 * Initial prep for release 4.1.3	2 years ago
Johannes Schindelin	aadec89964	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>	2 years ago
Simon Baird	8b5e8b7687	Support fetching without the --progress option (#1067 ) Setting the `show-progress` option to false in the `with` section of the workflow step will cause git fetch to run without `--progress`. The motivation is to be able to suppress the noisy progress status output which adds many hundreds of "remote: Counting objects: 85% (386/453)" and similar lines in the workflow log. This should be sufficient to resolve #894 and its older friends, though the solution is different to the one proposed there because it doesn't use the --quiet flag. IIUC git doesn't show the progress status by default since the output is not a terminal, so that's why removing the --progress option is all that's needed. Adding the --quiet flag doesn't make a lot of difference once the --progress flag is removed, and actually I think using --quiet would suppress some other more useful output that would be better left visible. Signed-off-by: Simon Baird <sbaird@redhat.com>	2 years ago
Robert Wieczoreck	7739b9ba2e	Add option to fetch tags even if fetch-depth > 0 (#579 ) * Add option to fetch tags even if fetch-depth > 0 * Add jest tests for fetchDepth and fetchTags options	2 years ago
Johannes Schindelin	d106d4669b	Add support for sparse checkouts (#1369 ) * Add support for sparse checkouts * sparse-checkout: optionally turn off cone mode While it _is_ true that cone mode is the default nowadays (mainly for performance reasons: code mode is much faster than non-cone mode), there _are_ legitimate use cases where non-cone mode is really useful. Let's add a flag to optionally disable cone mode. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> * Verify minimum Git version for sparse checkout The `git sparse-checkout` command is available only since Git version v2.25.0. The `actions/checkout` Action actually supports older Git versions than that; As of time of writing, the minimum version is v2.18.0. Instead of raising this minimum version even for users who do not require a sparse checkout, only check for this minimum version specifically when a sparse checkout was asked for. Suggested-by: Tingluo Huang <tingluohuang@github.com> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> * Support sparse checkout/LFS better Instead of fetching all the LFS objects present in the current revision in a sparse checkout, whether they are needed inside the sparse cone or not, let's instead only pull the ones that are actually needed. To do that, let's avoid running that preemptive `git lfs fetch` call in case of a sparse checkout. An alternative that was considered during the development of this patch (and ultimately rejected) was to use `git lfs pull --include <path>...`, but it turned out to be too inflexible because it requires exact paths, not the patterns that are available via the sparse checkout definition, and that risks running into command-line length limitations. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> --------- Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Co-authored-by: Daniel <daniel.fernandez@feverup.com>	2 years ago
SKi	47fbe2df0a	Fix: Checkout fail in self-hosted runners when faulty submodule are checked-in (#1196 ) * Fix Self hosted runner issue wrt bad submodules - solution cleanup working space. * Fix format with npm run format output * Add mock implementation for new function submoduleStatus * Add 2 test cases for submodule status. * Codeql-Action Analyse revert v1 to v2 --------- Co-authored-by: Bassem Dghaidi <568794+Link-@users.noreply.github.com> Co-authored-by: sminnie <minnie@sankhe.com>	2 years ago
Cory Miller	8856415920	Implement branch list using callbacks from exec function (#1045 ) When trying to list local branches to figure out what needs cleaned up during runs on non-ephemeral Actions Runners, we use git rev-parse --symbolic-full-name to get a list of branches. This can lead to ambiguous ref name errors when there are branches and tags with similar names. Part of the reason we use rev-parse --symbolic-full-name vs git branch --list or git rev-parse --symbolic seems to related to a bug in Git 2.18. Until we can deprecate our usage of Git 2.18, I think we need to keep --symbolic-full-name. Since part of the problem is that these ambiguous ref name errors clog the Actions annotation limits, this is a mitigation to suppress those messages until we can get rid of the workaround.	3 years ago
eric sciple	ec3a7ce113	set insteadOf url for org-id (#621 )	4 years ago
Thomas Boop	a81bbbf829	Remove unneeded commit information from build logs (#345 ) * Remove unneeded commit information from stdout	5 years ago
eric sciple	1433f62caa	update default branch (#305 )	5 years ago
eric sciple	fb6f360df2	fix default branch for .wiki and when using ssh (#284 )	5 years ago
eric sciple	e52d022eb5	Fetch all history for all tags and branches when fetch-depth=0 (#258 )	5 years ago
eric sciple	2ff2fbdea4	telemetry for incorrect merge commit (#253 )	5 years ago
eric sciple	422dc45671	add support for submodules (#173 )	6 years ago
eric sciple	f219062370	more unit tests and corresponding refactoring (#174 )	6 years ago
eric sciple	ae525b2262	fix issue checking detached when git less than 2.22 (#128 )	6 years ago
eric sciple	c170eefc26	add input persist-credentials (#107 )	6 years ago
eric sciple	a572f640b0	fallback to REST API to download repo (#104 )	6 years ago
eric sciple	e347bba93b	Convert checkout to a regular action (#70 )	6 years ago

20 Commits (ff7abcd0c3c05ccf6adc123a8cd1fd4fb30fb493)