What user problem are we solving?
As a part of the Github Action Revamp project, our goal is to centralize our Github Actions build checks ("CI" aspect) for frontend, backend, serverless along with our automated deploy actions to AWS (the "CD" aspect)
What solution does this PR provide?
This PR aims to centralize our backend checks into a backend.yml file. The action is structured such that the lint job runs before the test job in order to optimize on runtime.
Central Backend Check YML File
What user problem are we solving? As a part of the Github Action Revamp project, our goal is to centralize our Github Actions build checks ("CI" aspect) for frontend, backend, serverless along with our automated deploy actions to AWS (the "CD" aspect)
What solution does this PR provide? This PR aims to centralize our backend checks into a backend.yml file. The action is structured such that the lint job runs before the test job in order to optimize on runtime.
Testing Methodology Tested that the Github Action runs successfully in the ubuntu host. https://github.com/DSGT-DLP/Deep-Learning-Playground/actions/runs/6255227149/job/16984225135
Any other considerations Poetry env isn't getting cached properly with micromamba setting. We should somehow fix this in a followup PR.
We should also delete the following yml files in a followup PR as they've been migrated to backend.yml
black.yml
python-static-checker.yml
python-package-poetry.yml