Skip to content

Commit

Permalink
Merge pull request #55 from briederer/master
Browse files Browse the repository at this point in the history
Fix: Problem with relative path on Windows #54
  • Loading branch information
tpapp authored Jul 27, 2024
2 parents 9a7f571 + ec26c9e commit 0407e1a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/LocalCoverage.jl
Original file line number Diff line number Diff line change
Expand Up @@ -255,7 +255,7 @@ function generate_coverage(pkg = nothing;
mkpath(COVDIR)
tracefile = joinpath(COVDIR, LCOVINFO)
CoverageTools.LCOV.writefile(tracefile, coverage)
CoverageTools.clean_folder("./")
CoverageTools.clean_folder(package_dir)
eval_coverage_metrics(coverage, package_dir)
end
end
Expand Down

2 comments on commit 0407e1a

@tpapp
Copy link
Collaborator Author

@tpapp tpapp commented on 0407e1a Jul 27, 2024

Choose a reason for hiding this comment

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

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

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

Registration pull request created: JuliaRegistries/General/111866

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.8.1 -m "<description of version>" 0407e1a58286402a7d994bfc6ada40bd65351669
git push origin v0.8.1

Please sign in to comment.