ci: force bash as default shell in container jobs
CI / Test (rest) (pull_request) Failing after 56s
CI / Test (store) (pull_request) Successful in 37s
CI / Lint (pull_request) Successful in 17s
CI / Test (server-http) (pull_request) Successful in 2m0s
CI / Build (windows/amd64) (pull_request) Successful in 26s
CI / Build (linux/amd64) (pull_request) Successful in 28s
CI / Build (linux/arm64) (pull_request) Successful in 26s
e2e / Playwright vs docker-compose (pull_request) Failing after 3m47s
CI / Test (rest) (pull_request) Failing after 56s
CI / Test (store) (pull_request) Successful in 37s
CI / Lint (pull_request) Successful in 17s
CI / Test (server-http) (pull_request) Successful in 2m0s
CI / Build (windows/amd64) (pull_request) Successful in 26s
CI / Build (linux/amd64) (pull_request) Successful in 28s
CI / Build (linux/arm64) (pull_request) Successful in 26s
e2e / Playwright vs docker-compose (pull_request) Failing after 3m47s
When jobs run with `container:` set, Gitea Actions defaults to `sh -e` (dash on Ubuntu), so `set -euo pipefail` fails with "Illegal option -o pipefail". Pinning bash workflow-wide matches what the runner used pre-container and keeps existing scripts portable.
This commit is contained in:
@@ -54,6 +54,13 @@ on:
|
||||
pull_request:
|
||||
branches: [main]
|
||||
|
||||
# Force bash as the default shell. With `container:` set on every
|
||||
# job, Gitea Actions otherwise picks `sh -e` and our `set -euo
|
||||
# pipefail` fails on dash with "Illegal option -o pipefail".
|
||||
defaults:
|
||||
run:
|
||||
shell: bash
|
||||
|
||||
jobs:
|
||||
test:
|
||||
# Sharded by package group. server/http and store are the two
|
||||
|
||||
Reference in New Issue
Block a user