Changes workflow to not write the .env to its own variable to avoid a bug caused by gitea's runner exposing env vars #4

Merged
jamie merged 2 commits from fix/changes-env-file-handling into main 2026-04-15 12:40:33 +00:00
Showing only changes of commit afc56d6e1d - Show all commits
+1 -1
View File
@@ -62,7 +62,7 @@ runs:
if [ "$ENV_VAR" = "DOT_ENV" ] && [ -n "${{ inputs.dot-env-path }}" ]; then if [ "$ENV_VAR" = "DOT_ENV" ] && [ -n "${{ inputs.dot-env-path }}" ]; then
mkdir -p "$(dirname "${{ inputs.dot-env-path }}")" mkdir -p "$(dirname "${{ inputs.dot-env-path }}")"
umask 077 umask 077
printf '%s' "$SECRET_VALUE" > "${{ inputs.dot-env-path }}" printf '%s\n' "$SECRET_VALUE" > "${{ inputs.dot-env-path }}"
echo "Stored $SECRET_ID in $ENV_VAR file" echo "Stored $SECRET_ID in $ENV_VAR file"
else else
echo "$ENV_VAR<<EOF" >> $GITHUB_ENV echo "$ENV_VAR<<EOF" >> $GITHUB_ENV