run linting and tests on every push to every branch

[jadudm]

Problem

When developing, it is better to know early if your code is failing to pass checks that are required to go to production.

How did we discover this problem?

By... having this feature on other projects.

Job Story(s)

When I am developing my code, I want to have checks and tests run in a production-like deploy so I can keep my code in a ready-to-review state throughout the development process.

What are we planning to do about it?

This action is already mostly developed, but we want to make sure it is named appropriately, managed appropriately, and conforms to any style/practices that other actions will follow.

What are we not planning to do about it?

We are not planning to not do it.

How will we measure success?

Tasks

Preview Give feedback

1. run linting on every push to every branch
2. run tests on every push to every branch

Security Considerations

Required per CM-4.

None in particular, or similar to #85. There are likely fewer/no secrets involved in simply linting and testing.

---

Process checklist

• Has a clear story statement
• Can reasonably be done in a few days (otherwise, split this up!)
• Shepherds have been identified
• UX youexes all the things
• Design designs all the things
• Engineering engineers all the things
• Meets acceptance criteria
• Meets QASP conditions
• Presented in a review
• Includes screenshots or references to artifacts
• Tagged with the sprint where it was finished
• Archived

If there's UI...

• Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
• Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
• Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.