Align with spec-python-projects#158
Draft
ehanson8 wants to merge 1 commit into
Draft
Conversation
ehanson8
force-pushed
the
spec-align-2026-07
branch
from
July 7, 2026 13:44
9e4e14b to
e5ea28c
Compare
Why these changes are being introduced: * Aligning this repo with our current best practices represented by spec-python-projects How this addresses that need: * Various updates produced by running the /mitlib-spec-align-project skills which were reviewed and successfully tested. Side effects of this change: * NA Relevant ticket(s): * NA
ehanson8
force-pushed
the
spec-align-2026-07
branch
from
July 7, 2026 13:53
e5ea28c to
3545331
Compare
ehanson8
marked this pull request as draft
July 7, 2026 15:17
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.
PENDING GH WORKFLOW FIX
Purpose and background context
Aligning this repo with our current best practices represented by our Python repo spec
How can a reviewer manually see the effects of these changes?
The updated ECR image was pushed to
Stage(Dev1can't connect to the Data Warehouse) and successfully tested on 2026-07-06, Cloudwatch logs.Includes new or updated dependencies?
YES
Changes expectations for external applications?
NO
What are the relevant tickets?
Code review