Tested all common drush commands as well as the custom va ones listed in the readme file that is linked below. Some commands are specific to other groups within va and those have been flagged below as needing further testing.
Screenshots
QA steps
What needs to be checked to prove this works? check that modules have updated and drush commands still work
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?
Definition of Done
[ ] Documentation has been updated, if applicable.
[ ] Tests have been added if necessary.
[ ] Automated tests have passed.
[ ] Code Quality Tests have passed.
[ ] Acceptance Criteria in related issue are met.
[ ] Manual Code Review Approved.
[ ] If there are field changes, front end output has been thoroughly checked.
Select Team for PR review
[x] 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?
[ ] Yes, and it's written in issue ____ and queued for publication.
[ ] Merge and ping the UX writer so they are ready to publish after deployment
[ ] Yes, but it hasn't yet been written
[ ] Don't merge yet -- ping the UX writer to write and queue content
[ ] No announcement is needed for this code change.
Description
CLOSES #18728
Testing done
Tested all common drush commands as well as the custom va ones listed in the readme file that is linked below. Some commands are specific to other groups within va and those have been flagged below as needing further testing.
Screenshots
QA steps
What needs to be checked to prove this works? check that modules have updated and drush commands still work What needs to be checked to prove it didn't break any related things? What variations of circumstances (users, actions, values) need to be checked?
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?