Skip to content

Commit f0e7fd4

Browse files
committed
Remove unnecessary line continuation escaping from workflow
It is often necessary to escape the newline for continuation when breaking shell commands into multiple lines for readability. However, if a line break occurs in a shell command in an unterminated command, the continuation is implicit. The escaping in these shell commands was unnecessary and only made them a bit more cryptic, since the brackets already clearly indicate the structure
1 parent e6c0b7b commit f0e7fd4

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

.github/workflows/publish-go-tester-task.yml

+3-3
Original file line numberDiff line numberDiff line change
@@ -39,9 +39,9 @@ jobs:
3939
run: |
4040
RELEASE_BRANCH_REGEX="refs/heads/[0-9]+.[0-9]+.x"
4141
# The `create` event trigger doesn't support `branches` filters, so it's necessary to use Bash instead.
42-
if [[ \
43-
"${{ github.event_name }}" != "create" || \
44-
"${{ github.ref }}" =~ $RELEASE_BRANCH_REGEX \
42+
if [[
43+
"${{ github.event_name }}" != "create" ||
44+
"${{ github.ref }}" =~ $RELEASE_BRANCH_REGEX
4545
]]; then
4646
# Run the other jobs.
4747
RESULT="true"

0 commit comments

Comments
 (0)