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
{{ message }}
Repository navigation
[Infra] .github/codecov.yml sets frontend target to 'auto' while backend/contracts use fixed percentages, giving frontend no real coverage floor #1078
In .github/codecov.yml, the frontend flag's coverage target is auto (meaning "don't regress from the base commit"), while backend is pinned to 60% and contracts to 70%. A PR that starts from a low-coverage baseline can keep frontend coverage low indefinitely since auto never asks it to reach a fixed floor, unlike the other two flags.
Acceptance criteria
Decide and document a minimum frontend coverage floor consistent with current frontend coverage
Update frontend.target in .github/codecov.yml to a fixed percentage (or explicitly document why auto is intentional)
Verify the Codecov status check still passes on a recent PR
Congratulations, @emarkees! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @emarkees: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
Activity
IfyJustin91 commentedon Aug 21, 2026
Hi, I would like to work on this issue
emarkees commentedon Sep 27, 2026
@emarkees has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @emarkees to this issue.
drips-wave commentedon Sep 29, 2026
Congratulations, @emarkees! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @emarkees: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
grantfox-oss commentedon Oct 27, 2026
🎉 This issue has been marked as completed on GrantFox!
@emarkees's PR #1594 was approved and merged by @K1NGD4VID.
🏆 @emarkees: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (882 total points). Track your full progress on GrantFox.
👏 Great work, @emarkees! Keep contributing to LabsCrypt.