-
Notifications
You must be signed in to change notification settings - Fork 53
How to Review and Test Pull Requests for Dependabot
shanice-skylight edited this page Jun 12, 2024
·
2 revisions
Prerequisite - These instructions assume you have reviewed the procedures for deploying in order to deploy code to a dev or test environment (See Reference: https://github.com/CDCgov/prime-simplereport/wiki/Deploy)
- Select the Pull Request(PR) Dependabot created
- For the package identified in the PR, verify that this package is present within the codebase.
-
Deploy the PR code to a dev or test environment
-
Complete the following tests identified in this Bug bash document (https://docs.google.com/document/d/16cfE6gsslhcgvH3-Gi9LfkL85FQ-hEMPBkpLzR9dWWw/edit#heading=h.x3o4nsu2ptqi)
-
If any of the Github actions tests or Bug bash test have failed, this PR is not ready for deployment and should be troubleshooted and fixed.
-
In the event the dependabot PR gets stuck complete the following steps:
- Delete the branch
- Restore the branch
- Reopen the Pull Request
- This will trigger the Github actions test to re run.
- Complete the PR review
- Getting Started
- [Setup] Docker and docker compose development
- [Setup] IntelliJ run configurations
- [Setup] Running DB outside of Docker (optional)
- [Setup] Running nginx locally (optional)
- [Setup] Running outside of docker
- Accessing and testing weird parts of the app on local dev
- Accessing patient experience in local dev
- API Testing with Insomnia
- Cypress
- How to run e2e locally for development
- E2E tests
- Database maintenance
- MailHog
- Running tests
- SendGrid
- Setting up okta
- Sonar
- Storybook and Chromatic
- Twilio
- User roles
- Wiremock
- CSV Uploader
- Log local DB queries
- Code review and PR conventions
- SimpleReport Style Guide
- How to Review and Test Pull Requests for Dependabot
- How to Review and Test Pull Requests with Terraform Changes
- SimpleReport Deployment Process
- Adding a Developer
- Removing a developer
- Non-deterministic test tracker
- Alert Response - When You Know What is Wrong
- What to Do When You Have No Idea What is Wrong
- Main Branch Status
- Maintenance Mode
- Swapping Slots
- Monitoring
- Container Debugging
- Debugging the ReportStream Uploader
- Renew Azure Service Principal Credentials
- Releasing Changelog Locks
- Muting Alerts
- Architectural Decision Records
- Backend Stack Overview
- Frontend Overview
- Cloud Architecture
- Cloud Environments
- Database ERD
- External IDs
- GraphQL Flow
- Hibernate Lazy fetching and nested models
- Identity Verification (Experian)
- Spring Profile Management
- SR Result bulk uploader device validation logic
- Test Metadata and how we store it
- TestOrder vs TestEvent
- ReportStream Integration
- Feature Flag Setup
- FHIR Resources
- FHIR Conversions
- Okta E2E Integration
- Deploy Application Action
- Slack notifications for support escalations
- Creating a New Environment Within a Resource Group
- How to Add and Use Environment Variables in Azure
- Web Application Firewall (WAF) Troubleshooting and Maintenance
- How to Review and Test Pull Requests with Terraform Changes