Repository navigation
feat(pipeline): add devops main CI workflow - #8
Merged
Merged
Conversation
…infrastructure and build processes
…it step for database readiness
nourabosaif
approved these changes
Mar 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ci: add devops main CI workflow
What changed
Adds one GitHub Actions workflow file to
.github/workflows/:devops.yml— triggers on PRs targetingmainWhat the pipeline does
devops.yml(2 jobs)validate-structure— confirms all required DevOps files are present:docker/docker-compose.yml,docker/docker-compose.backend.yml,docker/docker-compose.frontend.yml, backend and frontend Dockerfiles, all scripts (bash + PowerShell), andenvironments/.env.example. Also validates that.env.examplecontains all 20 required environment variable keys.integration— clones the backend and frontend repos, writes a CI.envfile with safe non-sensitive values, starts the infrastructure viabash scripts/start-infra.sh, builds services viabash scripts/build.sh, starts the backend, runs migrations and seeds, smoke checksGET /healthfor{"status":"ok"}, collects Docker logs on failure, then tears everything down viabash scripts/stop.shWhy
The DevOps repo is the integration point for the entire platform. This pipeline validates that the infrastructure scripts, Compose files, and Dockerfiles all work together end-to-end before any changes are merged. It is the closest thing to a full local environment test that runs automatically.