-
Notifications
You must be signed in to change notification settings - Fork 3
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
192: Workflows #195
192: Workflows #195
Conversation
evan-scales
commented
Jan 20, 2024
•
edited
Loading
edited
- Created build-workflow
- Build, publish, upload artifacts, and tests api
- runs lint on spa, (later will be updated to run spa behavioral tests), auto formats code
- Created release-workflow
- Deploys SPA and API to azure whenever we bring changes to prod branch
- Tested both workflows, see past runs
Why the prod branch? Real world software is released on a cycle. Feature branches arn't merged to the master branch then released and deployed right away. Typically when it's time for a release changes are brought over to the release branch from master, then the app is redeployed based on the release branch. Prod will be our release branch |
If this has never actually succeeded in running, are you sure it will actually work when the checks pass? The failing tests probably should be fixed before we merge this so we can verify it will work. |
Its the linter thats failing, everything still works. Just tells us errors like' |
linter errors fixed |
Tests ran successfully! |
Run formatter on build-spa |
Be sure to stop failing pr's from being able to be merged. |