-
Notifications
You must be signed in to change notification settings - Fork 10
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
Update cross-val logic for tribal data consent form #2283
Merged
Merged
Conversation
This file contains 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
Terraform plan for meta No changes. Your infrastructure matches the configuration.
📝 Plan generated in Pull Request Checks #1126 |
Terraform plan for dev No changes. Your infrastructure matches the configuration.
📝 Plan generated in Pull Request Checks #1126 |
Minimum allowed coverage is Generated by 🐒 cobertura-action against f8cb148 |
jperson1
approved these changes
Sep 29, 2023
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 3, 2023
* Tribal audit consent form, first pass * What is code without linting? * Rename files/classes. Update to match Figma. * no-late-changes id change. * Djlint autoformat tribal data release * Title, not date. * Name/title side by side. Title moved out of grey box * Fix grey box boundary. Underline grey box title * We out here, linting python files * Validate against schema on upload. Copy updates * Checklist tribal data release description * add function for tribal audit form+add to full sub * tribal data consent cross-val * Grey box encompasses all questions * Remove-old-wkbks-edit tri-audit-form+gen-info.js * tribal data consent cross-val (#2283) * add two functions for tribal audi public & private * Submission Progress Check - Tribal Data Release (#2310) * Submission progress check - tribal data release * Edit link for tribal data release. * Tribal release above validation * Don't err if no auditee certifier is found. * remove is_public from audit model (#2319) * Cypress - New Report ID Format and Tribal Fix (#2366) * Remove pre-release instructions from prod deploy notes (#2328) * Resume mocking SAM.gov call (#2360) We meant to mock this and when we changed to using requests.session we missed updating the mock call in api/test_views.py. This wasn't detected because the actual call to SAM.gov would work—until this week, when the larger volume of SAM.gov API calls from actual users as well as our tests pushed us past the rate limit. Co-authored-by: Tadhg O'Higgins <2626258+tadhg-ohiggins@users.noreply.github.com> * Tribal - sign out/in as auditee, then as auditor * Cypress - New regex for report_ids * Oops, committed a local JWT. * Change tribal audit to private and not in API --------- Co-authored-by: Dan Swick <daniel.swick@gsa.gov> Co-authored-by: Tadhg O'Higgins <2626258+tadhg-ohiggins@users.noreply.github.com> Co-authored-by: Edward Zapata <edward.zapata@gsa.gov> --------- Co-authored-by: Edward Zapata <edward.zapata@gsa.gov> Co-authored-by: danswick <daniel.swick@gsa.gov> Co-authored-by: Tadhg O'Higgins <2626258+tadhg-ohiggins@users.noreply.github.com>
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.
closes #2103
PR checklist: submitters
main
into your branch shortly before creating the PR. (You should also be mergingmain
into your branch regularly during development.)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.