Open TylerHendrickson opened 1 week ago
Pusher: @TylerHendrickson, Action: pull_request_target
, Workflow: Continuous Integration
See our documentation for tips on how to resolve failing QA checks.
QA Check | Result |
---|---|
🌐 Web Tests | ✅ |
🔗 API Tests | ✅ |
🐍 Python Tests | ✅ |
📏 ESLint | ✅ |
🧼 Ruff | ✅ |
🛁 mypy | ✅ |
🧹 TFLint | ✅ |
View the workflow summary for individual coverage reports if this comment is truncated.
api
suiteweb
suitePusher: @TylerHendrickson, Action: pull_request_target
, Workflow: Continuous Integration
Step | Result |
---|---|
🖌 Terraform Format & Style | ✅ |
⚙️ Terraform Initialization | ✅ |
🤖 Terraform Validation | ✅ |
📖 Terraform Plan | ✅ |
Hint: If "Terraform Format & Style" failed, run terraform fmt -recursive
from the terraform/
directory and commit the results.
This PR adds configuration for dependency management via Dependabot, which is currently only configured in repository to respond to security updates. The new configuration will enable automatic dependency management for the following Dependabot ecosystems:
npm
(includes support for yarn). This is a multi-directory setup that includesapi/package.json
,web/package.json
, and the shared/yarn.lock
files.pip
(includes poetry support)terraform
(note this provides top-/project-level support only; should be fine since our terraform defines no custom module subdirectories)github-actions
All ecosystems share the same schedule, which will run Dependabot daily at 3am Eastern (
America/New_York
).Finally, this PR also includes a new GitHub Actions workflow,
Dependabot auto-approve
, which has identical behavior to the workflows with the same name that already exist in usdigitalresponse/usdr-gost and usdigitalresponse/grants-ingest repositories. As the name suggests, the purpose of this workflow is to automatically approve and merge pull requests from Dependabot where possible and sensible – in particular, auto-approval/-merge will only be enabled forminor
andpatch
Semver changes (not formajor
version upgrades). Additionally, other repository rules, such asCODEOWNERS
configuration, may require extra approval steps – unfortunately, this means that GitHub Actions dependency updates will not be automatically merged.