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
Every good project has some sort of Continuous Integration (CI) pipeline to make sure the code going in is good. CI is a way to automate linting and testing so it doesn't have to be performed manually. In this task, you will be using GitHub Actions to set up a CI pipeline that lints all incoming code. This page may provide some templates you could find useful. Ignore Continuous Delivery (CD) for now.
Requirements
Use GitHub Actions
CI pipeline should run ES Lint and Prettier on all code
Extra Credit
Have the CI pipline build the frontend and run the test in frontend\src\App.test.js (feel free to adjust this test if it isn't passing -- you can run it using npm test). Building and testing is the most common feature of CI, so this may actually be a good starting point since there are more templates for it
The text was updated successfully, but these errors were encountered:
Every good project has some sort of Continuous Integration (CI) pipeline to make sure the code going in is good. CI is a way to automate linting and testing so it doesn't have to be performed manually. In this task, you will be using GitHub Actions to set up a CI pipeline that lints all incoming code. This page may provide some templates you could find useful. Ignore Continuous Delivery (CD) for now.
Requirements
Extra Credit
npm test
). Building and testing is the most common feature of CI, so this may actually be a good starting point since there are more templates for itThe text was updated successfully, but these errors were encountered: