Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add code coverage to CI #3

Merged
merged 1 commit into from
Aug 31, 2023
Merged

Conversation

Jamstah
Copy link
Collaborator

@Jamstah Jamstah commented Aug 31, 2023

No description provided.

Makefile Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
Makefile Show resolved Hide resolved
@thaJeztah
Copy link
Member

Actually starting to wonder if we should combine workflows, so that we're not doing a git-clone for each (I see GitHub actions is already throttling (waiting for runners), which could be reduced if we run the steps after each-other (single "checkout", then run build, test, coverage)

@Jamstah
Copy link
Collaborator Author

Jamstah commented Aug 31, 2023

Yes, we should probably do that. Will give it a go now.

@Jamstah Jamstah force-pushed the coverage branch 2 times, most recently from b5fcb1b to fc87e43 Compare August 31, 2023 10:34
.github/workflows/go.yml Outdated Show resolved Hide resolved
.github/workflows/go.yml Outdated Show resolved Hide resolved
.github/workflows/test.yml Show resolved Hide resolved
.github/workflows/test.yml Outdated Show resolved Hide resolved
Makefile Show resolved Hide resolved
@Jamstah Jamstah force-pushed the coverage branch 4 times, most recently from a64231d to a65c481 Compare August 31, 2023 11:03
@thaJeztah
Copy link
Member

Last version looks good to me; should we merge the commits? The first commit is now adding a file which is immediately removed the commit after; I think for this case, it makes it still clear what's happening if we we combined the two; WDYT?

@thaJeztah
Copy link
Member

(either that, or flip the commits, but I expect that would be "possibly hairy" to do)

@Jamstah
Copy link
Collaborator Author

Jamstah commented Aug 31, 2023

Squashed.

Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

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

LGTM

@thaJeztah
Copy link
Member

@milosgajdos ready to go?

@milosgajdos milosgajdos merged commit 49c2849 into distribution:main Aug 31, 2023
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants