-
Notifications
You must be signed in to change notification settings - Fork 71
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
VACMS-20371: Clean up extensions #20730
Conversation
Checking composer.lock changes... |
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.
Early, unrequested feedback...
...t/modules/custom/va_gov_batch/src/cbo_scripts/RemoveNonNumericalCharactersFromExtensions.php
Show resolved
Hide resolved
docroot/modules/custom/va_gov_batch/src/cbo_scripts/SplitExtensionWithTwoNumbers.php
Show resolved
Hide resolved
Checking composer.lock changes... |
Checking composer.lock changes... |
Checking composer.lock changes... |
Checking composer.lock changes... |
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.
Code looks good and the QA steps all passed without any errors or notices. I doubled checked the Drupal logs to ensure nothing was intriguing there. Nice work.
Checking composer.lock changes... |
Checking composer.lock changes... |
Checking composer.lock changes... |
Cypress Accessibility Violations
|
Description
Relates to #20371
Testing done
Screenshots
QA steps
drush sqlc
use tugboat
exit
drush codit-batch-operations:run RemoveNonNumericalCharactersFromExtensions
drush codit-batch-operations:run SplitExtensionWithTwoNumbers
Spot check extensions in the following nodes to confirm that no non-numerical characters are in extensions
Check for remaining extensions
drush sqlc
use tugboat
Definition of Done
Select Team for PR review
CMS Team
Public websites
Facilities
User support
Accelerated Publishing
Is this PR blocked by another PR?
DO NOT MERGE
Does this PR need review from a Product Owner
Needs PO review
CMS user-facing announcement
Is an announcement needed to let editors know of this change?