fix: quote "on" key in YAML to prevent boolean parsing
Some checks failed
CI/CD Pipeline / Code Format (push) Failing after 1s
CI/CD Pipeline / Clippy Lints (push) Failing after 3s
CI/CD Pipeline / Unit Tests (push) Failing after 2s
CI/CD Pipeline / Build Debian Package (push) Has been skipped
CI/CD Pipeline / Build RPM Package (push) Has been skipped
CI/CD Pipeline / Build Alpine Package (push) Has been skipped
CI/CD Pipeline / Build Arch Package (push) Has been skipped
CI/CD Pipeline / Security Audit (push) Failing after 5s
Some checks failed
CI/CD Pipeline / Code Format (push) Failing after 1s
CI/CD Pipeline / Clippy Lints (push) Failing after 3s
CI/CD Pipeline / Unit Tests (push) Failing after 2s
CI/CD Pipeline / Build Debian Package (push) Has been skipped
CI/CD Pipeline / Build RPM Package (push) Has been skipped
CI/CD Pipeline / Build Alpine Package (push) Has been skipped
CI/CD Pipeline / Build Arch Package (push) Has been skipped
CI/CD Pipeline / Security Audit (push) Failing after 5s
YAML 1.1 reserves "on" as a boolean keyword (meaning True). Without quotes, Gitea Actions could not parse workflow triggers, resulting in no jobs being scheduled. This quotes the key as "on": to ensure it is parsed as a string event trigger key.
This commit is contained in:
@ -1,6 +1,6 @@
|
||||
name: CI/CD Pipeline
|
||||
|
||||
on:
|
||||
"on":
|
||||
push:
|
||||
branches: [ master, develop ]
|
||||
tags: [ 'v*' ]
|
||||
|
||||
Reference in New Issue
Block a user