publicdata/j40-cejst-2
1
0
Fork 0
mirror of https://github.com/DOI-DO/j40-cejst-2.git synced 2025-02-23 01:54:18 -08:00
Code Issues Projects Releases Packages Wiki Activity Actions
j40-cejst-2/.github/workflows
History
Vim d5a15f1053
Update side panel copy to Living copy (#1285) 
* Update side panel copy to Living copy

* Update lead paint short description

* Rebase main and update areaDetail snapshots

* Update cypress test on dataset used in beta header

* QA review updates

* Update deploy-fe-main to point to new CDN (d3r)
2022-02-17 10:59:23 -08:00
..
closed_fe_pr.yml Github Actions for Staging Backend (#1281) 2022-02-16 16:40:25 -05:00
codeql-analysis.yml Create codeql-analysis.yml 2021-07-19 09:21:28 -04:00
combine-tilefy.yml Update combine-tilefy.yml 2021-11-30 15:03:07 -05:00
compile_mermaid.yml Update compile_mermaid.yml (#65) 2021-05-19 18:41:48 -04:00
data-checks.yml Tox Security Fix (#1242) 2022-02-03 17:05:51 -05:00
deploy_be_staging.yml zip package update 2022-02-17 11:10:15 -05:00
deploy_fe_main.yml Update side panel copy to Living copy (#1285) 2022-02-17 10:59:23 -08:00
deploy_fe_staging.yml Github Actions for Staging Backend (#1281) 2022-02-16 16:40:25 -05:00
e2e.yml updates filename and comments (#378) 2021-07-19 08:05:32 -07:00
generate-census.yml Update generate-census.yml 2021-11-30 13:49:21 -05:00
generate-score.yml adding generate score back 2022-02-16 17:37:36 -05:00
main.yml Update main.yml (#704) 2021-09-17 10:06:59 -04:00
markdown-link-check.yml Run markdown link checker only on markdown changes (#1117) 2022-01-12 13:01:52 -05:00
README.md Update documentation to make it easier for users to find the right content for them (#1016) 2021-12-16 10:16:28 -05:00

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.