Skip to content

Adjust code coverage to only occur on a CRON schedule daily - #7720

Merged
dhaney-stacks merged 4 commits into
stacks-network:mainfrom
dhaney-stacks:main
Oct 9, 2026
Merged

dhaney-stacks merged 4 commits into
stacks-network:mainfrom
dhaney-stacks:main

Conversation

@dhaney-stacks

Copy link
Copy Markdown
Collaborator

Description

Adjust code coverage to only occur on a CRON schedule daily. We want accurate code coverage to be reported (and badged on our repo README), but we don't need to run it every PR or merge. It adds 4 minutes to the CI pipeline and we never take any action based on the results.

Applicable issues

N/A

Additional info (benefits, drawbacks, caveats)

N/A

Checklist

N/A

hstove-stacks
hstove-stacks previously approved these changes Oct 9, 2026

@hstove-stacks hstove-stacks left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great to see it's such an easy change!

@brice-stacks brice-stacks left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks mostly good, but I had a few comments for improvements. We also could update the build flags for the regular runs so that they no longer run with code coverage. I think that would touch more places, so it's fine if you want to do that in a separate PR.

Comment thread .github/workflows/ci.yml Outdated
Comment thread .github/workflows/ci.yml Outdated
Comment thread .github/workflows/ci.yml Outdated

@brice-stacks brice-stacks left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@dhaney-stacks
dhaney-stacks added this pull request to the merge queue Oct 9, 2026
Merged via the queue into stacks-network:main with commit 2a18ae8 Oct 9, 2026
366 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants