ci: add PR checks and PostgreSQL integrity coverage - #32
Merged
Merged
Conversation
Signed-off-by: debpalash <4178343+debpalash@users.noreply.github.com>
Signed-off-by: debpalash <4178343+debpalash@users.noreply.github.com>
Signed-off-by: debpalash <4178343+debpalash@users.noreply.github.com>
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
1 participant
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.
Pull requests previously had no automated checks. Add a read-only CI workflow for pull requests and pushes to main that runs the SQLite backend suite, PostgreSQL integrity/tenancy tests, frontend API tests, and monorepo lint/build with frozen dependency installs.
Add PostgreSQL regressions that force eight concurrent create requests through the unique-key recovery path and verify company merge/undo preserves linked people, fresh committed evidence, and observations added after merging. These run through a restricted application role with FORCE RLS.
Validation: 1,878 backend tests passed (131 skipped); 18 PostgreSQL tests passed on PostgreSQL 18.6; two frontend API tests passed; monorepo lint and build passed. The workflow provisions its own PostgreSQL service and uses no deployment credentials.