Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependabot-updates.md #16000

Merged
merged 2 commits into from
Sep 27, 2024
+1 −1
Merged

Update dependabot-updates.md #16000

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2d21eb1
Update dependabot-updates.md
snesm Sep 25, 2024
e54d50a
Merge branch 'master' into snesm/typo
snesm Sep 27, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion prime-router/docs/docs-deprecated/playbooks/dependabot-updates.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Please pay attention to [security related dependency PRs](https://github.com/CDC

## Steps
1. Open the dependabot's pull request to be merged and identify if the PR is out of date from master. If so, create a new comment in the PR with the text
`@dependabot rebase` to let dependabot rebase the branch for you. If you use any other method, dependabot will not be able to keep track of the PR. If the PR has conflicts (and no manual commits were added), use `@dpendabot recreate` to recreate the PR from scratch.
`@dependabot rebase` to let dependabot rebase the branch for you. If you use any other method, dependabot will not be able to keep track of the PR. If the PR has conflicts (and no manual commits were added), use `@dependabot recreate` to recreate the PR from scratch.
1. Verify that the build for the PR is successful. Note that the unit, integration and smoke tests are run as part of the build.
1. Read the updated library's changelog and identify and communicate any risks you find. When in doubt ask! Library changes can affect many parts of the system.
1. Identify any library version conflicts for the updated library. This may happen when other libraries are dependent on a different version of the same library. See
Expand Down
Loading