Skip to content

Conversation

zacharyburnett
Copy link
Contributor

@zacharyburnett zacharyburnett commented Feb 1, 2024

this PR should be kept as a draft until after #588 is merged, then rebased onto develop

changes in this PR:

  • added build.yml workflow that runs on pull requests, and also on releases (when on a release it also uploads the built wheel to PyPI - this requires that a PYPI_TOKEN with push permission for this repo be added to the repo secrets in Settings)
  • added steps to the end of test.yml that upload the frozen requirements.txt for that test session to two places:
    • as an artifact attached to every run
    • if triggered by a release, to the Assets section of that release
  • run tests in test.yml in parallel, and with coverage
  • upload coverage report to Codecov (needs CODECOV_TOKEN for this repo to be added to the repo secrets in Settings; this can be set up at codecov.io). This step can be removed if you don't want to use codecov to track coverage over time

@pep8speaks
Copy link

pep8speaks commented Feb 1, 2024

Hello @zacharyburnett, Thank you for updating !

Line 59:1: E265 block comment should start with '# '
Line 120:5: E123 closing bracket does not match indentation of opening bracket's line
Line 124:1: E265 block comment should start with '# '
Line 129:1: E265 block comment should start with '# '
Line 132:1: E265 block comment should start with '# '
Line 137:1: E265 block comment should start with '# '
Line 141:1: E265 block comment should start with '# '

Line 19:1: W391 blank line at end of file

Line 6:2: W292 no newline at end of file

Comment last updated at 2024-02-01 17:55:04 UTC

@zacharyburnett zacharyburnett changed the base branch from main to develop February 1, 2024 17:56
@codecov-commenter
Copy link

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

@zacharyburnett zacharyburnett marked this pull request as ready for review May 7, 2024 14:54
@zacharyburnett zacharyburnett force-pushed the workflows/build branch 3 times, most recently from 42d4295 to 5f471f6 Compare July 3, 2025 13:43
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