You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enhance deployment workflow with deploy ignore, concurrency support, and security fixes
- Add support for user-supplied .deployignore files and added built-in
ignore rules
- Exclude sensitive files by default (Steam credentials, .git/)
- Add an option for concurrent staging paths with commit SHA to avoid
conflicts with concurrent deployments (disabled by default)
- Update manifest generation to use filtered staging directory
- Add rsync installation in Dockerfile (used for .deployignore)
- Added verbosity a control for rsync operations.
Copy file name to clipboardExpand all lines: action.yml
+26-1Lines changed: 26 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,27 @@ inputs:
30
30
path:
31
31
required: false
32
32
default: ''
33
-
description: 'The path of the directory to be uploaded, relative to the repository root.'
33
+
description: 'The path of the directory containing the files you wish to upload, relative to the repository root.'
34
+
deployIgnore:
35
+
required: true
36
+
default: ''
37
+
description: 'The path of the deploy ignore file. Paths in this file are not included in the deployment. If a value is not supplied, will attempt to read a file named `.deployignore` from the root of the supplied path.'
38
+
useBuiltinDeployIgnore:
39
+
required: true
40
+
default: 'true'
41
+
description: 'Enables the built-in .deployignore rules to exclude common sensitive files during deployment. This is combined with the file supplied in `deployIgnore`'
42
+
stagingPath:
43
+
required: true
44
+
default: '/tmp/steam_deploy/'
45
+
description: 'The staging directory. Files will be copied from your `path` to here before being uploaded. Anything excluded under your .deployIgnore rules will not be copied here, and as such will not be packaged with your deployed artifact. This directory is not cleared when this workflow finishes.'
46
+
concurrentStaging:
47
+
required: true
48
+
default: 'false'
49
+
description: 'If `true`, the `stagingPath` will include the commit SHA as a subdirectory, ensuring each deployment uses its own isolated path and avoiding conflicts between concurrent deployments. Useful for self-hosted or nonephemeral actions runners. This directory is not cleared when this workflow finishes'
50
+
verbosity:
51
+
required: true
52
+
default: "NORMAL"
53
+
description: 'Sets the log verbosity. Can be either `NORMAL` or `TRACE`. If invalid, will behave as `TRACE`.'
0 commit comments