Read-only mirror — the public repositories of the Forgejo instance, refreshed every 10 minutes. The live instance (fg.dieschoenewolke.de) is reachable only over the VPN; clone here with https://git.dieschoenewolke.de/git/<owner>/<repo>.git.
summaryrefslogtreecommitdiff
path: root/README.md
AgeCommit message (Collapse)Author
2026-06-17getting ready for checkout v7 release (#2464)Aiqiao Yan
* getting ready for checkout v7 release * update changelog wording Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
2026-06-16block checking out fork pr for pull_request_target and workflow_run (#2454)Aiqiao Yan
* block checking out fork pr for some events * address copilot and reviewer feedback * run prettier formatting * build * update urls * update readme * update description and url again * edit url one more time
2025-12-01Clarify v6 README (#2328)v6.0.1eric sciple
2025-11-23Update all references from v5 and v4 to v6 (#2314)eric sciple
- Updated README.md examples to reference @v6 - Updated all workflow files to use actions/checkout@v6
2025-11-20update readme/changelog for v6 (#2311)v6.0.0eric sciple
2025-11-03v6-beta (#2298)v6-betaeric sciple
2025-08-13Update README to include Node.js 24 support details and requirements (#2248)Salman Chishti
* Update README to include Node.js 24 support details and requirements * Update
2025-08-11Prepare v5.0.0 release (#2238)v5.0.0Salman Chishti
2025-06-06Update README.md (#2194)Ben De St Paer-Gotch
2025-01-16Adjust positioning of user email note and permissions heading (#2044)Josh Gross
2025-01-16Documentation update - add recommended permissions to Readme (#2043)Ben Wells
* Update README.md * Update README.md Co-authored-by: Josh Gross <joshmgross@github.com> --------- Co-authored-by: Josh Gross <joshmgross@github.com>
2024-11-14Update README.md (#1977)Mohammad Ismail
2024-11-08docs: update README.md (#1971)The web walker
Add a scenario where it is necessary to push a commit to a pull request.
2024-09-02Provide explanation for where user email came from (#1869)yasonk
* Provide explanation for where user email came from * bringing back the newline
2024-04-30README: Suggest `user.email` to be ↵v4.1.5Cory Miller
`41898282+github-actions[bot]@users.noreply.github.com` (#1707) * README: Set `user.email` to GitHub Actions Bot * Update workflow to use proper bot GitHub Bot email * Prefix `user.email` with `41898282+` To match squash merge user, else showing as two different users, see: https://github.com/SocketDev/socket-sdk-js/commit/b0948d0da0cfb5b240c69d063cc34a6399abce48 * Update README.md --------- Co-authored-by: Pelle Wessman <pelle@kodfabrik.se>
2024-04-18Add SSH user parameter (#1685)v4.1.3Cory Miller
* Add a configurable SSH user * Update docs with param * Indentation of readme * formatting woes * Update src/url-helper.ts Co-authored-by: Josh Gross <joshmgross@github.com> * Update action.yml Co-authored-by: Josh Gross <joshmgross@github.com> * Update genfiles --------- Co-authored-by: Josh Gross <joshmgross@github.com>
2023-10-17Link to release page from what's new section (#1514)v4.1.1Cory Miller
2023-10-13Correct link to GitHub Docs (#1511)Peter Bengtsson
No hardcoded language in the URL and uses the correct docs.github.com domain.
2023-09-22Add support for partial checkout filters (#1396)Finley Garton
* added filter option & tests * added build file * fix test oversight * added exit 1 * updated docs to specify override * undo unneeded readme change * set to undefined rather than empty string * run git config in correct di --------- Co-authored-by: Cory Miller <13227161+cory-miller@users.noreply.github.com>
2023-09-05Update README.md for V4 (#1452)Varun Sivapalan
* Update README.md for V4 * Update actionReference in generate-docs.ts for v4
2023-09-01Support fetching without the --progress option (#1067)Simon Baird
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>
2023-08-16Add option to fetch tags even if fetch-depth > 0 (#579)Robert Wieczoreck
* Add option to fetch tags even if fetch-depth > 0 * Add jest tests for fetchDepth and fetchTags options
2023-06-09Add support for sparse checkouts (#1369)Johannes Schindelin
* 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>
2022-12-16Add in explicit reference to private checkout options (#1050)Ryan van Zeben
2022-10-17README - fix status badge (#967)Scott Brenner
2022-09-26Inject GitHub host to be able to clone from another GitHub instance (#922)Peter Murray
* Adding the ability to specify the GitHub Server URL and allowing for it to differ from the Actions workflow host * Adding tests for injecting the GitHub URL * Addressing code review comments for PR #922
2022-04-20Add set-safe-directory input to allow customers to take control. (#770)Tingluo Huang
* Add set-safe-directory input to allow customers to take control.
2022-03-01update readme for v3 (#708)v3.0.0Thomas Boop
* update readme for v3 * update readme with changes * nit grammar
2021-11-02Change secret name for PAT to not start with GITHUB_ (#623)Ameya Lokare
Github doesn't allow secret names that start with `GITHUB_` (case insensitive). Update README to choose a different prefix (GH).
2020-07-14Update README.mderic sciple
2020-07-14Update README.mderic sciple
2020-07-14update default branch (#305)eric sciple
2020-07-12improve description for fetch-depth (#301)mastereric sciple
2020-06-16determine default branch (#278)eric sciple
2020-05-27Fetch all history for all tags and branches when fetch-depth=0 (#258)eric sciple
2020-05-20fix readme (#251)eric sciple
2020-03-19update readmeeric sciple
2020-03-19Removed doc based on new changes (#192)Jef LeCompte
2020-03-12persist core.sshCommand for submodules (#184)eric sciple
* persist core.sshCommand for submodules * update verbiage; add comments * fail when submodules or ssh-key and fallback to REST API
2020-03-11add ssh support (#163)eric sciple
2020-03-05add support for submodules (#173)eric sciple
2020-02-13Handle submodules with SSH URLs (#140)Christopher Sexton
* Handle submodules with SSH URLs This is just a documentation change, explaining how to fix submodules that are configured to use SSH URLs instead of HTTPS URLs. Spent a while banging my head on the wall and hope this saves someone else the pain. This is helpful for teams that use the SSH protocol for local development so don't want to change the mechanism that pulls in the submodules. Using `insteadOf` seems a bit nicer than than setting up a deploy keypair. * SSH submodules Co-authored-by: Chris Patterson <chrispat@github.com>
2020-01-03Add link to doc for creating and using encyrpted secrets (#123)eric sciple
2020-01-02improve summary (#127)eric sciple
2019-12-16example fetch all history for all tags and branches (#115)eric sciple
2019-12-13add more scenarios (#112)eric sciple
2019-12-13update examples to reference v2 tag (#110)v2.0.0eric sciple
2019-12-12add input persist-credentials (#107)eric sciple
2019-12-12fallback to REST API to download repo (#104)eric sciple
2019-12-10Document update: Checkout PR head sha (#102)Riddhesh Sanghvi