Brian Rutledge
Brian Rutledge
Re: Codacy, a quick search through their docs yields [support for coverage.py](https://github.com/codacy/codacy-coverage-reporter#supported-formats). However, it's also a general-purpose code-quality tool, indicating things like security and code style issues. Perhaps more than...
> if we care about this, we should pick a % and start asserting on it in CI. > This is the old school way that I never understood why...
Agreed re: the caveats of 100% coverage. Re: publishing an HTML report, I wondered if [GitHub Action artifacts](https://help.github.com/en/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts) would help. [A GitHub search](https://github.com/search?q=path%3A.github+upload-artifact+htmlcov&type=Code) led me to this example, where it's...
Had a chat with @nedbat about this at Boston Python Office Hours; he had a similar wish, without a solution beyond the downloadable ZIP artifacts mentioned above. For now, I'm...
For future reference, Hynek wrote about switching from Codecov to uploading coverage.py artifacts in [How to Ditch Codecov for Python Projects](https://hynek.me/til/ditch-codecov-python/).
That does seem like a long list. Related: - [Prepare for 3.3 release by jaraco · Pull Request #682 · pypa/twine](https://github.com/pypa/twine/pull/682) - [Fix/mitigate flaky integration tests · Issue #684 ·...
Having just released 3.3.0 using my local command line (as instructed by https://twine.readthedocs.io/en/latest/contributing.html#making-a-new-release), I'm curious about moving more/all of that to GitHub, via Releases and Actions. For example, I was...
@sigmavirus24 I think the overloading of the term "releases" might be causing some confusion. To clarify, I'm not advocating for replacing PyPI as the distribution mechanism. In fact, I'm not...
Those are excellent points; happy to set GitHub Releases aside. Thanks for indulging me.
On a whim, I created a lightweight release for 3.4.2 at https://github.com/pypa/twine/releases, which simply links to the PyPI page and the changelog. This feels like minimal overhead to make releases...