ci: make validation compatible with Gitea runner
All checks were successful
CI / Validate frontend and API (push) Successful in 37s
All checks were successful
CI / Validate frontend and API (push) Successful in 37s
This commit is contained in:
@@ -32,4 +32,4 @@ Public course endpoints return only public lessons and public assets. Enrolment
|
||||
|
||||
## CI/CD status
|
||||
|
||||
GitHub Actions validates every pull request and every push to `main` by installing locked dependencies, type-checking the frontend and API, building the frontend, and uploading the production build as an artifact. Deployment remains intentionally unconfigured until the frontend and API hosting providers are chosen.
|
||||
Gitea Actions validates every pull request and every push to `main` by installing locked dependencies, type-checking the frontend and API, and building the frontend. The workflow deliberately does not upload a build artifact: the current Gitea runner does not support `upload-artifact@v4`, and Portainer builds the deployment image directly from the repository.
|
||||
|
||||
Reference in New Issue
Block a user