Add set-safe-directory input to allow customer to take control. by TingluoHuang · Pull Request #770 · actions/checkout (original) (raw)
me-and added a commit to cygporter/git that referenced this pull request
This fix should allow setting safe.directory manually and not having it overridden by the actions/checkout action. Test the behaviour works as expected for both the Cygwin runner (with a manually set safe.directory in the Git config file) and the Ubuntu runner (with no explicit safe.directory wrangling).
Disable build steps that are unnecessary / slow / would produce permanent changes. Enable steps that we want to check with this action even though they'd normally only be run for actual releases (subject to the previous caveat).
TingluoHuang added a commit that referenced this pull request
- Add set-safe-directory input to allow customers to take control.
TingluoHuang added a commit that referenced this pull request
… (#776)
- Add set-safe-directory input to allow customers to take control.
jackton1 added a commit to jackton1/github-push-action that referenced this pull request
This has been resolved in the checkout action and would already be set by default.
This was referenced
Jun 14, 2022
caarlos0 added a commit to goreleaser/goreleaser that referenced this pull request
Bumps actions/checkout from 3 to 3.0.2.
Release notes Sourced from actions/checkout's releases.
v3.0.2 What's Changed
Add set-safe-directory input to allow customers to take control. by @TingluoHuang in actions/checkout#770 Prepare changelog for v3.0.2. by @TingluoHuang in actions/checkout#777
Full Changelog: actions/checkout@v3...v3.0.2 v3.0.1
Fixed an issue where checkout failed to run in container jobs due to the new git setting safe.directory Bumped various npm package versions
Changelog Sourced from actions/checkout's changelog.
Changelog v3.0.2
Add input set-safe-directory
v3.0.1
Fixed an issue where checkout failed to run in container jobs due to the new git setting safe.directory Bumped various npm package versions
v3.0.0
Update to node 16
v2.3.1
Fix default branch resolution for .wiki and when using SSH
v2.3.0
Fallback to the default branch
v2.2.0
Fetch all history for all tags and branches when fetch-depth=0
v2.1.1
Changes to support GHES (here and here)
v2.1.0
Group output Changes to support GHES alpha release Persist core.sshCommand for submodules Add support ssh Convert submodule SSH URL to HTTPS, when not using SSH Add submodule support Follow proxy settings Fix ref for pr closed event when a pr is merged Fix issue checking detached when git less than 2.22
v2.0.0
Do not pass cred on command line Add input persist-credentials Fallback to REST API to download repo
v2 (beta)
Improved fetch performance
... (truncated)
Commits
See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Carlos Alexandro Becker caarlos0@users.noreply.github.com
This was referenced
Aug 30, 2022
ZPascal pushed a commit to ZPascal/github-push-action that referenced this pull request
This has been resolved in the checkout action and would already be set by default.
Update README.md
Fix removed code lines
- Add force with lease support
- Update the documentation
fix: github_token and github_url optional
Add atomic push
Since time elapses between the checkout the github workflow performs and the eventual push this action invokes the remote HEAD may have changed. If this is the case the HEAD update will be rejected but any tag (and their commits) will be pushed.
In general I think this operation should be atomic, either we push everything or we push nothing.
Force pushes still work the way you would expect (i.e. if we force the HEAD update with --atomic everything is still pushed)
This also protects from the situation where someone else has seized your tag name in the meantime but not updated your HEAD.
See git docs for more information - https://git-scm.com/docs/git-push#Documentation/git-push.txt---no-atomic
Add option to control atomic switch
Use node16 to run action
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
Update the documentation and the push process
feat: Restructure the code
Update the documentation and the push process
lurch added a commit to lurch/checkout that referenced this pull request
vanZeben pushed a commit that referenced this pull request
This was referenced
Jan 17, 2023
vbraun pushed a commit to vbraun/sage that referenced this pull request
bjoernboettle pushed a commit to bjoernboettle/checkout that referenced this pull request
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})