j40-cejst-2/.github/workflows
2024-12-10 10:56:46 -06:00
..
closed_be_pr.yml rm backend staging folder 2022-02-17 17:36:48 -05:00
closed_fe_pr.yml Github Actions for Staging Backend (#1281) 2022-02-16 16:40:25 -05:00
codeql-analysis.yml Changes to allow local runs 2024-12-04 21:28:51 -05:00
combine-tilefy.yml PyPi Packaging of Data Pipeline (#1464) 2022-03-21 18:55:15 -04:00
compile_mermaid.yml Fix broken YML links and add PR template (#1340) 2022-02-25 11:39:38 -08:00
create-score-version.yml Backend release branch to main (#1822) 2022-12-01 21:50:54 -05:00
deploy_backend_main.yml Merge branch 'main' into nmb/backend-rollout-plans 2024-12-10 10:56:46 -06:00
deploy_be_staging.yml Add ability to compare scores (#2172) 2023-02-21 16:50:31 -06:00
deploy_fe_main.yml update Spanish content (#2203) 2023-06-27 09:42:39 -07:00
deploy_fe_staging.yml update Spanish content (#2203) 2023-06-27 09:42:39 -07:00
deploy_frontend_main.yml Add PR build checks, disable deploy concurrency 2024-12-09 15:18:28 -05:00
e2e.yml minor workflow changes to update action versions 2024-12-04 21:30:05 -05:00
generate-census.yml Backend release branch to main (#1822) 2022-12-01 21:50:54 -05:00
generate-score.yml Update generate-score.yml 2022-04-27 10:49:56 -04:00
main.yml Backend release branch to main (#1822) 2022-12-01 21:50:54 -05:00
markdown-link-check.yml Multiple workflow fixes 2024-12-04 21:29:43 -05:00
pr_backend.yml Force use of matrix in GitHub Action job names 2024-12-09 15:19:14 -05:00
pr_frontend.yml Force use of matrix in GitHub Action job names 2024-12-09 15:19:14 -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
refresh-be-cdn.yml Modify data tile server to static URL to fix CORS (#1512) 2022-03-30 13:44:58 -07:00
tribal-deploy.yml Starting Tribal Boundaries Work (#1736) 2022-07-30 01:13:10 -04:00

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.