Repository navigation
Workflows/ci/bff - #11
Merged
Merged
Conversation
…d init cargo envirment and using slim docker
…on Reg Request and add field exppires_in Login Response
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.
Description
This PR introduces the foundational Continuous Integration (CI) pipeline for the BFF service. It sets up an automated workflow to ensure code quality, security, and test coverage before merging into the
devandmasterbranches.Pipeline Stages
The workflow consists of four primary jobs:
cargo fmt) and strict linting (clippy). Includesprotocinstallation to ensure gRPC schemas compile correctly.cargo audit.cargo llvm-cov.Important
This pipeline enforces strict quality gates. It is configured to fail the build if
clippythrows any warnings (-D warnings) or if the test code coverage falls below the 80% threshold.Note
To optimize GitHub Actions minutes, the workflow uses path filters. It will only trigger if changes are detected within
backend/service/bff_service/**,backend/libs/rust-core/**, orbackend/proto/**.Tip
Once this PR is merged, it is highly recommended to update the Branch Protection Rules for the
devbranch to require this CI workflow to pass successfully before any future pull requests can be merged.