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
Describe the bug
New coverage is appended at the top and get marked as Coverage 1. But it should be the Current total coverage + 1 ( like if there are 5 coverages, the new coverage should be 6th one).
If we are appending the latest coverage at the top, then it should be the n-th coverage ,not the first coverage.
Practically we should append the latest coverage at the last and give number accordingly.
Screenshots
Screen.Recording.2025-03-12.at.10.05.01.PM.mov
🚨 DO NOT EDIT BELOW THIS LINE 🚨
Instructions for Requesting Assignment:
To request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:
Describe your solution clearly:
Provide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.
Expected Timeline:
End date: [Expected submission date of a completed Pull Request]
Additional Context:
Include any other relevant context, links, screenshots, or resources that support your proposed solution.
🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.
The text was updated successfully, but these errors were encountered:
Describe the bug
New coverage is appended at the top and get marked as Coverage 1. But it should be the Current total coverage + 1 ( like if there are 5 coverages, the new coverage should be 6th one).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
Screen.Recording.2025-03-12.at.10.05.01.PM.mov
🚨 DO NOT EDIT BELOW THIS LINE 🚨
Instructions for Requesting Assignment:
To request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:
Describe your solution clearly:
Provide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.
Expected Timeline:
Additional Context:
Include any other relevant context, links, screenshots, or resources that support your proposed solution.
The text was updated successfully, but these errors were encountered: