Skip to content

Comments

Docstring coverage CI/CD (51)#84

Merged
tennlee merged 7 commits intoACCESS-Community-Hub:developfrom
JMP-MO:add-interrogate-51
Apr 3, 2025
Merged

Docstring coverage CI/CD (51)#84
tennlee merged 7 commits intoACCESS-Community-Hub:developfrom
JMP-MO:add-interrogate-51

Conversation

@JMP-MO
Copy link
Collaborator

@JMP-MO JMP-MO commented Apr 2, 2025

Added a github workflow which will:

  • Intall the interrogate package
  • Run the interrogate package with a pass rate of 40 currently (so it passes)
  • Output:
    • Detailed report text file.
    • Badge svg file.

There is an issue with the pre-commit workflow where it fails on the 'black' package. For this reason I moved this into its own workflow. However the interrogate workflow completes successfully.

Screenshot 2025-04-02 at 16 06 01

@JMP-MO
Copy link
Collaborator Author

JMP-MO commented Apr 2, 2025

I am guessing to add the badge to the project repo we would need to add, commit and push the badge file. Then add the file location to the readme? Is there a way to pick up the artifacts for this purpose?

@coveralls
Copy link

Pull Request Test Coverage Report for Build 14223291327

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 57.568%

Totals Coverage Status
Change from base Build 14196779914: 0.0%
Covered Lines: 7716
Relevant Lines: 13003

💛 - Coveralls

@tennlee
Copy link
Collaborator

tennlee commented Apr 3, 2025

I'll start by merging and make sure it runs through properly on the repo, then we can tackle the badging process subsequently.

@tennlee tennlee merged commit a98f098 into ACCESS-Community-Hub:develop Apr 3, 2025
6 of 7 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