DEV: add PostgreSQL CI for dev pull requests - #713
Merged
Conversation
TThanos3000
force-pushed
the
infra/dev-backend-postgresql-ci
branch
from
August 27, 2026 18:26
4d865ff to
0658925
Compare
TThanos3000
marked this pull request as ready for review
August 27, 2026 18:53
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.
Scope
Semantic port of PostgreSQL CI infrastructure from production PR #674 to the current
devbranch. Nomaster -> devmerge or broad cherry-pick was used.The new workflow:
dev;workflow_dispatch;select_for_updatesupport;vacancy.tests.test_vacancy_response_contract_apiwhen the PR DEV: harden vacancy responses and expose applicant state #712 module is present;The CI settings replace Redis cache, Redis Channels, Celery broker/result storage, and external email with in-process test implementations. HTTPS redirect and React-dev demo seeding are disabled only in the isolated CI settings module.
PostgreSQL compatibility adjustment
The first real PostgreSQL run exposed one pre-existing order-dependent assertion in
mailing.tests.test_models_rendering. The test expected database rows in insertion order although the contract does not define that order. It now verifies the same field keys and values by key, matching the production PR #674 adaptation. Mailing business code and behavior are unchanged. Tests from PR #712 are unchanged.Triggers
pull_requestwith basedev;workflow_dispatch.There is no
push,workflow_run,workflow_call, deploy, SSH, rsync, Docker build, or environment deployment trigger in the new workflow.Verification
Local:
black --checkfor changed Python files: passed;flake8for changed Python files: passed;python manage.py check --tag modelswithprocollab.settings_ci: passed;git diff --check: passed;GitHub Actions:
Scope confirmation
devSHA:5fc11e4871d218496362345fdcf288d2899e48dd.