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:
@@ -37,6 +37,11 @@ env:
|
||||
REGISTRY: gitea.dcglab.co.uk
|
||||
IMAGE_NAME: ${{ gitea.repository }}
|
||||
|
||||
# Force bash as the default shell — see ci.yml header.
|
||||
defaults:
|
||||
run:
|
||||
shell: bash
|
||||
|
||||
jobs:
|
||||
image:
|
||||
name: Build + push image
|
||||
|
||||
Reference in New Issue
Block a user