mirror of
https://github.com/DOI-DO/j40-cejst-2.git
synced 2025-02-22 17:44:20 -08:00
6425beb9f4
* starting yaml config load work * working version for downloadable file * yaml file update * checkpoint * sort if needed * refactoring * moving config * checkpoint * old files * skipping downloadble tests for now * more modularization * more refactor, new excel yml * pylint * completed tabs * Update excel.yml * remvoing obsolete tests * addressing PR feedback * addressing changes * confirmed change in yaml breaks tests * safety bump * PR review * adding tests back * pylint * Incorporating latest score fields from Emma * incorporating newest fields from Emma * passing tests * adding shapefile aws sync * missing test * passing tests |
||
|---|---|---|
| .. | ||
| closed_be_pr.yml | ||
| closed_fe_pr.yml | ||
| codeql-analysis.yml | ||
| combine-tilefy.yml | ||
| compile_mermaid.yml | ||
| data-checks.yml | ||
| deploy_be_staging.yml | ||
| deploy_fe_main.yml | ||
| deploy_fe_staging.yml | ||
| e2e.yml | ||
| generate-census.yml | ||
| generate-score.yml | ||
| main.yml | ||
| markdown-link-check.yml | ||
| README.md | ||
Justice40 Github Actions Workflows
This directory has the github actions workflows for the Justice40 Project.
This project is deployed on an AWS account managed by GeoPlatform.gov, and github actions is used to automate the data pipeline and all deployment steps.
The names of the Github Actions stages in the yaml files should describe what each step does, so it is best to refer there to understand the latest of what everything is doing.
To mitigate the risk of having this README quickly become outdated as the project evolves, avoid documenting anything application or data pipeline specific here. Instead, go back up to the top level project README and refer to the documentation on those components directly.