You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,7 +125,7 @@ Open a new pull request. Be sure to set the base branch to your fork.
125
125
**Step 7: Seeing Impact Analysis in the UI**
126
126
-------------
127
127
128
-
After CI/CD has completed, you should see a comment from Codecov. The comment will now show 2 new elements
128
+
After CI/CD has completed, you should see a comment from Codecov similar to this [PR](https://github.com/codecov/impact-analysis-example-python/pull/14). The comment will now show 2 new elements
129
129
130
130
1. Under `impacted files`, you should see a `Critical` label next to `example-app/utils/time.py`. This means that the PR has a change in that file that is frequently hit in production.
131
131
2. Under `related entrypoints`, you should see `/time`. This means that the PR has a change that touches that endpoint.
0 commit comments