You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -456,9 +456,7 @@ test differences between PyMongo's tests and the specification.
456
456
To be clear, changes listed in these patch files will be *undone* by the script, and thus won't
457
457
be added to pymongo.
458
458
459
-
In the case that a new test is added to the spec repo (i.e., a whole new file or folder in the spec repo),
460
-
and the associated work isn't implemented yet, we will add the test's path to
461
-
`.evergreen/remove-unimplemented-tests.sh` along with a comment indicating the associated PYTHON ticket.
459
+
When a new test file or folder is added to the spec repo before the associated code changes are implemented, that test's path must be added to `.evergreen/remove-unimplemented-tests.sh` along with a comment indicating the associated PYTHON ticket for those changes.
462
460
463
461
Any PR that implements a PYTHON ticket documented in a patch file or within `.evergreen/remove-unimplemented-tests.sh` must also remove the associated patch file or entry in `remove-unimplemented-tests.sh`.
0 commit comments