j40-cejst-2/.github/workflows
Shaun Verch 40dfe31f50 Add github action for testing generate score post
This doesn't take very long, even with the full dataset, so it might be
worth running this on every pull request commit.

Related to https://github.com/usds/justice40-tool/issues/599.
2022-01-07 16:25:12 -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 disabling data checks on non-data folders (#532) 2021-08-16 15:12:58 -04:00
deploy_main.yml Add build status badges to client README (#799) 2021-10-14 15:28:25 -07:00
deploy_staging.yml Remove GitHub pages deploy on staging (#891) 2021-11-16 09:58:53 -08: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 updating combtilefy 2021-11-02 12:06:06 -04:00
main.yml Update main.yml (#704) 2021-09-17 10:06:59 -04:00
markdown-link-check.yml 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 Update documentation to make it easier for users to find the right content for them (#1016) 2021-12-16 10:16:28 -05:00
test-generate-score-post.yml Add github action for testing generate score post 2022-01-07 16:25:12 -05: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.