ci: introduce full-stack GitHub Actions for Next.js frontend and Docker infrastructure#34
Open
chinmayy777 wants to merge 2 commits intoOSIPI:mainfrom
Open
ci: introduce full-stack GitHub Actions for Next.js frontend and Docker infrastructure#34chinmayy777 wants to merge 2 commits intoOSIPI:mainfrom
chinmayy777 wants to merge 2 commits intoOSIPI:mainfrom
Conversation
…ors and configure 100MB payload limit for BIDS uploads
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
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.
Motivation
With the recent migration of the repository and the establishment of backend regression tests, we need to ensure the Frontend UI and Deployment Infrastructure are equally protected.
Next.js is notoriously strict during production builds (e.g., failing on unused variables during ESLint checks), and Docker container environments can easily break from minor dependency mismatches. This PR introduces a CI pipeline to catch these "silent failures" before they can be merged into
main.What This PR Does
Adds a new
.github/workflows/frontend-infrastructure-ci.ymlworkflow that automatically runs on every push/PR tomain:yarndependencies.yarn lintto enforce strict React/Next.js code quality.yarn buildto guarantee the static production bundle successfully compiles without fatal errors.docker compose buildto verify that the multi-stage Dockerfiles for both frontend and backend resolve correctly in an isolated Ubuntu environment.Impact
This perfectly complements the backend API test coverage by providing 360-degree full-stack CI validation. Reviewers can now merge UI and Docker changes with absolute confidence that the local development environment and production builds will not break.