-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#2723: Copying e2e code from /dissemination
to /census_historical_migration
#2725
#2723: Copying e2e code from /dissemination
to /census_historical_migration
#2725
Conversation
Terraform plan for meta No changes. Your infrastructure matches the configuration.
✅ Plan applied in Deploy to Development and Management Environment #335 |
Terraform plan for dev No changes. Your infrastructure matches the configuration.
✅ Plan applied in Deploy to Development and Management Environment #335 |
Minimum allowed coverage is Generated by 🐒 cobertura-action against ff60250 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed while pairing with @sambodeme. Looks good as a first step 👍
Addresses epic #2672
Closes #2723
In this PR:
census_historical_migration
end_to_end_test_data_generator
andgenerate_workbook_files
from/dissemination
commands, and renaming them tohistoric_data_migrator
andhistoric_workbook_generator
workbooklib
from/dissemination
, and updating appropriate importsTesting:
docker compose run web python manage.py historic_data_migrator --email <your email>
PR checklist: submitters
main
into your branch shortly before creating the PR. (You should also be mergingmain
into your branch regularly during development.)git status | grep migrations
. If there are any results, you probably need to add them to the branch for the PR. Your PR should have only one new migration file for each of the component apps, except in rare circumstances; you may need to delete some and re-runpython manage.py makemigrations
to reduce the number to one. (Also, unless in exceptional circumstances, your PR should not delete any migration files.)PR checklist: reviewers
make docker-clean; make docker-first-run && docker compose up
; then rundocker compose exec web /bin/bash -c "python manage.py test"
The larger the PR, the stricter we should be about these points.