Add repo line count to coverage drip emails#714
Merged
hiroshinishio merged 1 commit intomainfrom Feb 26, 2026
Merged
Conversation
- Include approximate line count (e.g. ~8K lines) next to repo name in coverage chart emails - Track repoMostNeedingCoverageLines through owner context pipeline - Improve email copy: "just came in at" instead of "is", "reached" instead of "has" - Fix dora.dev 301 redirect flagged by Ahrefs
hiroshinishio
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
~8K lines) next to repo name in coverage chart drip emails so recipients understand project scalerepoMostNeedingCoverageLinesthrough the owner context pipeline