Skip to content

Commit 8ca5dc2

Browse files
authored
Update sub-bullets in dependency docs process steps (#709)
* Update indent of bullet in Renovate docs. * Converted ordered to unordererd list for consistency.
1 parent 705fbf6 commit 8ca5dc2

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

docs/contributing/dependencies/index.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -281,15 +281,13 @@ A typical dependency workflow involves the following steps:
281281
3. Review the release notes of each dependency, for each released version between the current and
282282
the proposed upgrade. Identify if there are any deprecations or breaking changes affecting our
283283
code.
284-
1. For **breaking changes**, either resolve them yourself, or for major changes, coordinate with
285-
the other teams.
286-
2. For **deprecations**, create high priority Jira tickets on the affected teams' backlogs with a
287-
due date at least one sprint before the next scheduled major release of the dependency.
284+
- For **breaking changes**, either resolve them yourself, or for major changes, coordinate with
285+
the other teams.
286+
- For **deprecations**, create high priority Jira tickets on the affected teams' backlogs with a
287+
due date at least one sprint before the next scheduled major release of the dependency.
288288
4. Verify CI status.
289-
290-
- This may also include re-running any failed workflows due to insufficient permissions when
291-
Renovate created the pull request.
292-
289+
- This may also include re-running any failed workflows due to insufficient permissions when
290+
Renovate created the pull request.
293291
5. If test coverage is lacking, check out locally and manually confirm a few key areas.
294292
6. Review the proposed code changes and approve the PR.
295293
7. Update the ticket to include testing notes for QA.

0 commit comments

Comments
 (0)