Actions: google/jimfs
Actions
Showing runs from all workflows
318 workflow runs
318 workflow runs
SecureDirectoryStream.move works like Files.move with the ATOMIC_MOVE option, as specified, and require Path arguments to SecureDirectoryStream methods to be from the same FileSystem as the stream itself. This also corrects it to not follow any symbolic links, again matching the behavior of Files.move.
Google GitHub Admin: Actions Workflow Security Scan
#40:
Pull request #482
synchronize
by
copybara-service
Bot
SecureDirectoryStream.move works like Files.move with the ATOMIC_MOVE option, as specified, and require Path arguments to SecureDirectoryStream methods to be from the same FileSystem as the stream itself. This also corrects it to not follow any symbolic links, again matching the behavior of Files.move.
CI
#727:
Pull request #482
synchronize
by
copybara-service
Bot
SecureDirectoryStream.move works like Files.move with the ATOMIC_MOVE option, as specified, and require Path arguments to SecureDirectoryStream methods to be from the same FileSystem as the stream itself. This also corrects it to not follow any symbolic links, again matching the behavior of Files.move.
GitHub Actions Scan
#13:
Pull request #482
synchronize
by
copybara-service
Bot
SecureDirectoryStream.move works like Files.move with the …
CI
#726:
Commit 398b0f9
pushed
by
copybara-service
Bot
SecureDirectoryStream.move works like Files.move with the ATOMIC_MOVE option, as specified, and require Path arguments to SecureDirectoryStream methods to be from the same FileSystem as the stream itself. This also corrects it to not follow any symbolic links, again matching the behavior of Files.move.
Google GitHub Admin: Actions Workflow Security Scan
#39:
Pull request #482
synchronize
by
copybara-service
Bot
SecureDirectoryStream.move works like Files.move with the ATOMIC_MOVE option, as specified, and require Path arguments to SecureDirectoryStream methods to be from the same FileSystem as the stream itself. This also corrects it to not follow any symbolic links, again matching the behavior of Files.move.
CI
#725:
Pull request #482
synchronize
by
copybara-service
Bot
SecureDirectoryStream.move works like Files.move with the ATOMIC_MOVE option, as specified, and require Path arguments to SecureDirectoryStream methods to be from the same FileSystem as the stream itself. This also corrects it to not follow any symbolic links, again matching the behavior of Files.move.
GitHub Actions Scan
#12:
Pull request #482
synchronize
by
copybara-service
Bot
SecureDirectoryStream.move works like Files.move with the ATOMIC_MOVE option, as specified, and require Path arguments to SecureDirectoryStream methods to be from the same FileSystem as the stream itself. This also corrects it to not follow any symbolic links, again matching the behavior of Files.move.
Google GitHub Admin: Actions Workflow Security Scan
#38:
Pull request #482
opened
by
copybara-service
Bot
SecureDirectoryStream.move works like Files.move with the ATOMIC_MOVE option, as specified, and require Path arguments to SecureDirectoryStream methods to be from the same FileSystem as the stream itself. This also corrects it to not follow any symbolic links, again matching the behavior of Files.move.
GitHub Actions Scan
#11:
Pull request #482
opened
by
copybara-service
Bot
SecureDirectoryStream.move works like Files.move with the ATOMIC_MOVE option, as specified, and require Path arguments to SecureDirectoryStream methods to be from the same FileSystem as the stream itself. This also corrects it to not follow any symbolic links, again matching the behavior of Files.move.
CI
#724:
Pull request #482
opened
by
copybara-service
Bot
Files.move so that ATOMIC_MOVE always enables overwriting of an existing destination file.
Google GitHub Admin: Actions Workflow Security Scan
#34:
Pull request #479
synchronize
by
copybara-service
Bot